Check your application dependencies
Tell ARGUNIS which folders hold your applications and it checks the libraries in their lockfiles against OSV advisories, with the version to upgrade to.
On this page
Application dependencies checks the libraries your applications use (what their lockfiles declare) against the public OSV vulnerability database and tells you which ones are affected and which version to upgrade to. It covers:
npm (Node.js):
package-lock.json,npm-shrinkwrap.json,yarn.lockandpnpm-lock.yaml.PyPI (Python):
requirements.txt(only lines with==),poetry.lockandPipfile.lock.Packagist (PHP):
composer.lock.Maven (Java):
pom.xml(only dependencies with an explicit version) andgradle.lockfile.NuGet (.NET):
packages.lock.jsonand.csprojfiles with an exact version.Go:
go.mod(orgo.sumif there is nogo.mod).RubyGems (Ruby):
Gemfile.lock.
Before you start
View permission on Vulnerabilities and the terms of use accepted.
Server agent 3.9.0 or later on the host where the applications are.
Permission to configure the agent (Infrastructure).
Set the folders of your applications
Go to Infrastructure, open the server and go to Agent → Configure plugins.
In General, enter one path per line in Application folders, for example
/srv/tiendaorC:\inetpub\api.Save. The agent looks for lockfiles in those folders within a few minutes and then every 6 hours.
The agent only reads those folders (up to 8 levels deep, without entering node_modules, vendor or .git) and sends the name, version and path of each dependency. It never uploads the files. It does not check what is inside Docker containers: set the folder on the host where the code is.
Review the advisories
Go to Security (SIEM) → Vulnerabilities → Application dependencies.
Filter by status (Open, Resolved or All), ecosystem, severity, server, application path, or check KEV only.
Review each row: the server, the lockfile it is in, the package and version, the advisory (CVE or OSV id) with its CVSS, and what to do.
Click the advisory to see its summary, its other names (CVE, GHSA) and the links.
Upgrade the dependency to the version shown in What to do and regenerate the lockfile. When the agent reports the new version, the advisory moves to Resolved on its own.
Start with the ones marked KEV: they are vulnerabilities that are already being exploited.
Automatic notifications
A KEV advisory opens a critical incident (or, if you have the SIEM, a critical detection with its case).
A critical advisory (CVSS 9 or higher) opens a warning incident (or a high detection).
You get a single notification per server, with the list: for example, «/srv/tienda/package-lock.json: lodash 4.17.15 (npm) — CVE-2021-23337 high (CVSS 7.2) — upgrade to 4.17.21».
It closes on its own when the server no longer has that version in its lockfiles.
You also see these advisories on the server page (Security).
Things to keep in mind
Only exact versions are checked: a range such as
>=2.0inrequirements.txtor[1.0,2.0)in a.csprojcannot be checked. Use a lockfile.In
pom.xmlonly the versions written in the same file count; for everything Maven resolves, usegradle.lockfileor keeppom.xmlwith explicit versions.If OSV does not state the fixing version, you will see No fixed version published.
Dependencies are checked when the agent reports a change and once a day. If the OSV lookup does not respond, the advisories stay as they were until the next check.