Audit Vulnerabilties
Audit Vulnerabilities is available as both a pgutil
command and an HTTP Request, and will audit packages individually or associated with a project file.
This example will audit vulnerabilities in the project MyProject.csproj
located locally in c:\projects\
:
pgutil vulns audit --project=c:\projects\MyProject.csproj
Note that vulnerability assessments are not available in ProGet Free edition and this API is subject to API limits in ProGet Basic edition. See License Restrictions to learn more.
Command Specification (CLI)
The vulns audit
command is used audit a project file. This command is intended to audit packages used as part of a build process. It should be run after building the project because it requires the presence of specific build tool output (i.e. a lockfile or similar artifact) to generate accurate data.
The --project
option is always required. The --type
option is optional and will filter by package type.
Auditing project vulnerabilities requires the project file name (e.g. myProject
).
pgutil vulns audit --project=c:\projects\MyProject.csproj
Running this command will asses the specified project and output the results:
Scanning for dependencies in projects/MyProject.csproj...
Found 2 package dependencies. Performing audit...
1 vulnerable package detected.
PGV-2245804: 7.5 (High) - Improper Handling of Exceptional Conditions in Newtonsoft.Json
* Packages: Newtonsoft.Json 12.0.3
* Projects: MyProject
HTTP Request Specification
If you disallow anonymous access to your feed, you will need to create an API Key that grants access to the Feed API. You will need to include that key as a header named X-ApiKey
and set its value to that API key.
For example, to authenticate with the API key abc12345
to this endpoint, you could specify the API key as follows:
curl -X POST -H "X-ApiKey: abc12345" https://proget.corp.local/api/sca/audit-package-vulns
To audit packages via the API, simply POST
to the URL with an appropriate API Key and an array of PackageVersionIdentifier objects as the request body.
POST /api/sca/audit-package-vulns
[
{
"name": myPackage
"version": 1.2.3
"type": "nuget"
},
{
"name": myPackage
"version": 1.2.3
"type": "nuget"
}
]
HTTP Response Specification
A successful (200
) response body will contain an array of VulnerabilityInfo objects. For example, auditing version 1.2.3
of the package myPackage
returns:
[
{
"id": "PGV-12345678",
"affectedPackages": [0],
"summary": "Improper Handling of Exceptional Conditions",
"published": "2022-06-22T15:08:47Z",
"details": "This is a vulnerability",
"cve": "CVE-1234-56789",
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"numericCvss": 7.5,
"severity": "High"
},
{
"id": "PGV-8765432",
"affectedPackages": [0,1],
"summary": "Improper Input Validation",
"published": "2022-06-22T15:08:47Z",
"details": "This is another vulnerability",
"cve": "CVE-9876-5432",
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"numericCvss": 7.5,
"severity": "High"
}
]
Response | Details |
---|---|
200 (Success) | the body will contain an array of VulnerabilityInfo objects |
400 (Invalid Input) | indicates invalid or missing properties in the request; the body will provide some details as text |
403 (Unauthorized API Key) | indicates a missing, unknown, or unauthorized API Key; the body will be empty |