CVE-2024-50611
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCycloneDX cdxgen through 10.10.7, when run against an untrusted codebase, may execute code contained within build-related files such as build.gradle.kts, a similar issue to CVE-2022-24441. cdxgen is used by, for example, OWASP dep-scan. NOTE: this has been characterized as a design limitation, rather than an implementation mistake.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCycloneDX cdxgen through 10.10.7 executes code embedded in build-related files (such as build.gradle.kts) when parsing untrusted codebases, allowing arbitrary code execution. This stems from a design flaw where the tool calls build system parsers that evaluate code rather than merely extracting metadata, similar to CVE-2022-24441.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if cdxgen is installedRun 'npm list -g cdxgen' or 'which cdxgen' to see if the tool is present on the systemAffected if cdxgen is installed on the system
-
Determine the installed cdxgen versionRun 'cdxgen --version' to get the exact version numberAffected if The version is 10.10.7 or any earlier version (e.g., 10.0.0, 9.x, 8.x)
-
Identify cdxgen usage patternsReview any scripts, CI/CD pipelines, or automation that invoke cdxgen to parse codebasesAffected if cdxgen is being run against external, untrusted, or third-party codebases containing build files like build.gradle.kts, pom.xml, or package.json
-
Verify build file parsing is occurringCheck if cdxgen commands include flags like '--detect-compose', '--detect-go-mod', '--detect-gradle', or auto-detection of build systemsAffected if cdxgen is actively parsing build configuration files from untrusted sources
-
Audit for recent cdxgen executions against untrusted inputReview logs, command history, or SIEM alerts for cdxgen executions against unknown or external repositoriesAffected if cdxgen has recently processed untrusted or unverified codebases containing build files
You are affected if cdxgen version 10.10.7 or earlier is installed AND the tool has been used to parse build files (such as build.gradle.kts) from untrusted or external codebases.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDo not run cdxgen against untrusted or unverified codebases; validate and sandbox inputs, or wait for the upstream design fix that separates parsing from execution.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data