Platform/SCA
SCA: one update closes several vulnerabilities
Matches project libraries against the vulnerability database and shows what to update.
CVE-2021-44228remote code execution
CVE-2021-45046code execution in certain configurations
CVE-2021-45105denial of service
One action Update log4j-core
2.14.1 → 2.17.1
closes three vulnerabilities 01How it works
From code to decision
- 01Inventorythe library composition from dependency files, without running the build
- 02Matchingagainst the vulnerability database inside the perimeter
- 03Reachabilitywhether your code calls the vulnerable function
- 04Fixfindings are grouped by update
- 05Decisionupdate, accept the risk with a deadline, or dismiss
02In the platform
Is the vulnerability reachable
- reachable
- A path from your code to the vulnerable library function is found.
- not reachable
- Proven: the library is not used or the vulnerable function is never called.
- undetermined
- There is no data on the vulnerable function, or there is doubt.
Vulnerabilities · payments-api group by by fix
Update log4j-core 2.14.1 → 2.17.1pom.xml · closes 3
confirmed Update jackson-databind 2.9.8 → 2.15.4pom.xml · closes 5
needs triage Update spring-web 5.3.18 → 6.1.14pom.xml · closes 2
needs triage Update commons-text 1.9 → 1.10.0pom.xml · closes 1
needs triage Update lodash 4.17.15 → 4.17.21web/package-lock.json · closes 3
fixed exampleseverity · basis · status
- By fix
- Findings are grouped: you see what to update and how many vulnerabilities it closes.
- Already exploited
- Vulnerabilities from the KEV catalog that are used in attacks are marked in the list.
- Major version
- You see when an update changes the library's major version.
- Reachability
- Currently for Java and Go. For other ecosystems the state is "undetermined".
- Composition inventory (SBOM)
- Downloaded from a scan in CycloneDX format. The download is recorded in the audit log.
- Database updates
- By signed archive or update channel.
Ecosystems
MavennpmPyPINuGetGoComposerCargoPubSwiftCocoaPods
Dependency files
pom.xmlbuild.gradlegradle.lockfilepackage-lock.jsonyarn.lockpnpm-lock.yamlrequirements*.txtpoetry.lockPipfile.lockuv.lockpackages.lock.jsonpackages.configgo.modcomposer.lockCargo.lockpubspec.lockPackage.resolvedPodfile.lock
04Report and perimeter
For the auditor and for your network
What goes into the report
- ARDFM No. 53, cl. 148. Analysis of components and third-party libraries completed without failures. The basis states the scan number.
- ARDFM No. 53, cl. 150. The number of components and ecosystems, how many were matched against the database and how many vulnerabilities were found.
- Order No. 111/NQ. Matching libraries against the CVE database.
Inside your perimeter
- No internet. The vulnerability database sits inside the perimeter. Matching runs with no outbound requests.
- Nothing is executed. Build tools and scripts from the repository are not run: dependency files are only read.
- What was not checked. Dependency files that SCA does not read yet are marked "not checked".