OpenstackApplication · Redhat
CVE-2013-6470
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 default configuration in the standalone controller quickstack manifest in openstack-foreman-installer, as used in Red Hat Enterprise Linux OpenStack Platform 4.0, disables authentication for Qpid, which allows remote attackers to gain access by connecting to Qpid.
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 default configuration in the standalone controller quickstack manifest of openstack-foreman-installer (used in Red Hat Enterprise Linux OpenStack Platform 4.0) disables authentication for the Qpid message broker, allowing remote unauthenticated attackers to connect and gain access to the messaging infrastructure.
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
OpenstackApplication
= 4.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Confirm OpenStack Platform versionRun 'cat /etc/redhat-release' or check the installed openstack packages version to verify the system is running Red Hat Enterprise Linux OpenStack Platform 4.0Affected if The installed version is Red Hat OpenStack Platform 4.0
-
Verify Qpid broker is installedCheck if the qpid-cpp-server package is installed by running 'rpm -qa | grep qpid-cpp' or check for the qpidd service with 'systemctl status qpidd'Affected if Qpid message broker is present on the system
-
Inspect Qpid authentication configurationExamine the Qpid configuration file typically located at /etc/qpidc.conf or /etc/qpid/qpidd.conf. Look for configuration parameters related to 'auth', 'authenticate', 'allow-anonymous', or 'acl-file'Affected if Authentication is explicitly disabled or commented out in the Qpid configuration
-
Check for anonymous access enabledSearch the Qpid configuration for settings like 'allow-anonymous=true' or 'auth=no' that would permit unauthenticated connectionsAffected if Anonymous access is permitted in the Qpid broker configuration
The system is affected if it is running Red Hat OpenStack Platform 4.0 with Qpid broker installed and authentication is disabled or anonymous access is allowed in the Qpid configuration.
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 dataEnable and enforce authentication for the Qpid broker in the quickstack configuration, ensuring all connections require valid credentials.
Fix this in Openstack
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6470 — 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-2013-6470 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