SatelliteApplication · Redhat
CVE-2024-3716
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 foreman-installer when puppet-candlepin is invoked cpdb with the --password parameter. This issue leaks the password in the process list and allows an attacker to take advantage and obtain the password.
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 confidenceA password leakage vulnerability exists in foreman-installer where passwords passed to puppet-candlepin's cpdb command via the --password parameter are exposed in the system process list. Any local attacker with access to the system can view running processes and capture these plaintext passwords.
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
SatelliteApplication
= 6.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify foreman-installer installation and versionRun 'rpm -qa | grep foreman-installer' or check /usr/sbin/foreman-installer --versionAffected if Version is 6.0 and the package is installed
-
Check for puppet-candlepin module usageSearch for cpdb command invocations in /etc/foreman-installer/custom-hiera.yaml, /etc/foreman-installer/applied.yaml, or look for scripts invoking 'cpdb --password'Affected if cpdb command is invoked with --password argument anywhere in foreman-installer configs or scripts
-
Inspect running processes for password exposureRun 'ps aux | grep -i cpdb' or 'ps aux | grep -i candlepin' during foreman-installer execution to check for plaintext passwords in process argumentsAffected if Any running process shows --password followed by a plaintext password in the command line
-
Review process listing for historical exposuresIf audit logs or process accounting are enabled, review /var/log/audit/audit.log or use 'ausearch' to search for cpdb/candlepin password patterns in past process executionsAffected if Historical process logs reveal plaintext passwords passed to cpdb --password parameter
If foreman-installer version 6.0 is installed and cpdb commands are executed with --password parameter visible in process list, the environment is affected by CVE-2024-3716.
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 dataModify the foreman-installer code to use secure password input methods (such as reading from stdin or environment variables) instead of passing passwords as command-line arguments to prevent exposure in the process list.
Fix this in Satellite
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3716 — 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-3716 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