FedoraOperating system · Fedoraproject
CVE-2022-3275
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 · uneditedCommand injection is possible in the puppetlabs-apt module prior to version 9.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterprise.
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 confidenceCommand injection vulnerability in the puppetlabs-apt module allows a malicious actor to execute arbitrary commands by providing unsanitized input. The vulnerability exists in versions prior to 9.0.0 and requires the attacker to have the ability to supply unsanitized input to the module, which is described as rare in typical deployments.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 36= 37< 9.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 puppetlabs-apt module versionRun `puppet module list` or check the module's metadata.json file in the modules directory to find the installed version of the puppetlabs-apt moduleAffected if The puppetlabs-apt module version is below 9.0.0 (e.g., 8.x, 7.x, etc.)
-
Check Puppet agent versionRun `puppet --version` to identify the Puppet agent version, then cross-reference with any bundled apt moduleAffected if The Puppet agent includes an apt module version prior to 9.0.0
-
Check operating system versionRun `cat /etc/fedora-release` or `hostnamectl` to identify the Fedora versionAffected if Running Fedora 36 or Fedora 37, as these versions contain the affected apt module
-
Assess input access to apt moduleReview who and what can supply input to the puppetlabs-apt module - check Puppet code, external fact suppliers, or any system that can pass parameters to apt module resourcesAffected if Untrusted or unsanitized input can be supplied to apt module resources (this condition makes exploitation possible)
A system is affected if it runs the puppetlabs-apt module version below 9.0.0 (or Fedora 36/37) AND allows untrusted input to reach the apt module.
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.
dbcve · scoped9.0.0
Upgrade the puppetlabs-apt module to version 9.0.0 or later. Additionally, restrict and validate all input provided to the apt module to prevent exploitation.
puppetlabs-apt module version 9.0.0 or later
- Identify the current version of the puppetlabs-apt module in use
- Upgrade the puppetlabs-apt module to version 9.0.0 or later using 'puppet module upgrade puppetlabs-apt --version 9.0.0' or your module management tool
- Verify the upgrade was successful by checking the installed module version
- Test the Puppet deployment to ensure the module functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3275 — 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-2022-3275 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