FedoraOperating system · Fedoraproject
CVE-2016-3696
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 · uneditedThe pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.
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 confidenceThe pulp-qpid-ssl-cfg script in Pulp versions before 2.8.5 insecurely exposes the Certificate Authority (CA) private key, allowing local unprivileged users to obtain this sensitive cryptographic material. This compromises the SSL/TLS trust chain for the Qpid messaging broker component.
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
= 24<= 2.8.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Check installed Pulp versionRun 'rpm -q pulp-server' or 'pulp-admin --version' to determine the Pulp version installedAffected if The version is 2.8.4 or lower, or if the package is not found but pulp-qpid-ssl-cfg script exists with old versioning
-
Locate the pulp-qpid-ssl-cfg scriptSearch for the script using 'find / -name pulp-qpid-ssl-cfg 2>/dev/null' or check common paths like /usr/bin/, /usr/local/bin/, or within the Pulp installation directoryAffected if The script exists on the system, indicating the Qpid SSL configuration component is present
-
Inspect CA key file permissionsIdentify CA private key files (typically named ca.key, ca_key.pem, or similar under /etc/pulp/qpid/ or /etc/qpid/ SSL directories), then run 'ls -la <ca_key_file>' to check permissionsAffected if The CA key file is readable or writable by non-root users (permissions show any permission for others or group beyond '---' or if owner is not root)
-
Check script world-readabilityRun 'ls -la <path-to-pulp-qpid-ssl-cfg>' to verify if the script itself or associated CA files are readable by any userAffected if The script or its associated CA key files have permissions allowing world read access (r--r--r-- or similar)
-
Verify Qpid broker configurationCheck if Qpid is configured and running alongside Pulp by running 'systemctl status qpidd' or inspecting /etc/pulp/qpid/ configuration filesAffected if Qpid messaging broker is in use with Pulp, making the CA key exposure actionable for SSL/TLS trust chain compromise
The system is affected if Pulp version 2.8.4 or earlier is installed and the pulp-qpid-ssl-cfg script or its associated CA private key files are accessible to non-root users.
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 dataUpgrade to Pulp 2.8.5 or later which contains the fix for secure CA key handling in the pulp-qpid-ssl-cfg script. As a compensating control, verify file permissions on any CA key files are restricted to root-only access.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3696 — 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-2016-3696 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