Code execution via invoked build scripts
Published Oct 27, 2024 · Updated Oct 30, 2024
Code injection during dependency analysis in CycloneDX cdxgen 10.10.7 and earlier allows attackers to execute code from a scanned codebase. During dependency analysis, cdxgen invokes npm, Maven, Gradle, and sbt, allowing repository-controlled build scripts and plugins to run in the cdxgen process context. Exploitation requires the target to scan attacker-controlled source, and the resulting code runs with the cdxgen process's privileges.
Summary
What happened
Code injection during dependency analysis in CycloneDX cdxgen 10.10.7 and earlier allows attackers to execute code from a scanned codebase. During dependency analysis, cdxgen invokes npm, Maven, Gradle, and sbt, allowing repository-controlled build scripts and plugins to run in the cdxgen process context. Exploitation requires the target to scan attacker-controlled source, and the resulting code runs with the cdxgen process's privileges.
The record
- CVE
- CVE-2024-50611
- Published
- Oct 27, 2024
- Updated
- Oct 30, 2024
- Vendor
- CycloneDX
- Product
- cdxgen
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 27, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=10.10.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- build.gradle.kts file-write proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo