CVE-2024-2307
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 · uneditedA flaw was found in osbuild-composer. A condition can be triggered that disables GPG verification for package repositories, which can expose the build phase to a Man-in-the-Middle attack, allowing untrusted code to be installed into an image being built.
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 · moderate confidenceosbuild-composer has a flaw where a specific condition can disable GPG verification for package repositories during the image build process. This exposes the build phase to Man-in-the-Middle attacks, allowing attackers to inject untrusted code into images being built.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L
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.
-
Confirm osbuild-composer is installedRun 'rpm -q osbuild-composer' (RHEL/Fedora) or 'dpkg -l osbuild-composer' (Debian) to check if the package is presentAffected if The package is not installed or the query returns no results, meaning this component is not in use
-
Identify the installed versionRun 'rpm -q --info osbuild-composer' (RHEL/Fedora) or 'dpkg -s osbuild-composer' (Debian) to retrieve the installed version numberAffected if The installed version falls within the vulnerable version range for CVE-2024-2307 (compare your version to the official vulnerability database)
-
Inspect repository configuration filesCheck /etc/osbuild-composer/repos.d/ and /etc/osbuild-composer/composer.conf for custom repository definitions; look for any entries with gpgcheck=False or gpgverify=False settingsAffected if Any repository configuration disables GPG verification (gpgcheck=False or gpgverify=False is present)
-
Review repository definitions in kickstart and blueprint filesExamine any .ks (kickstart) or .toml (blueprint) files used with osbuild-composer for repository definitions; search for 'gpgcheck' or 'gpgkeys' parametersAffected if Repository definitions in build inputs explicitly disable GPG verification or omit GPG key specifications
A system is affected if osbuild-composer is installed AND the version is vulnerable AND any repository configuration disables GPG verification, allowing MITM injection during image builds.
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 dataIdentify and remediate the code path that disables GPG verification; ensure GPG verification is always enforced for all package repositories in osbuild-composer configurations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2307 — 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-2307 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