CVE-2015-5223
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 · uneditedOpenStack Object Storage (Swift) before 2.4.0 allows attackers to obtain sensitive information via a PUT tempurl and a DLO object manifest that references an object in another container.
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 confidenceOpenStack Swift before version 2.4.0 contains an information disclosure vulnerability where attackers with a valid PUT tempurl (temporary URL) for one container can craft a Dynamic Large Object (DLO) manifest that references objects in a different container, thereby gaining unauthorized read access to objects they should not have permission to access.
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<= 2.3.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.
-
Identify OpenStack Swift versionRun 'swift --version' or check the installed package (e.g., 'rpm -q swift' or 'dpkg -l | grep swift') to determine the installed versionAffected if The installed version is 2.3.0 or earlier (versions <= 2.3.0)
-
Verify tempurl middleware is enabledInspect the proxy-server.conf file (typically in /etc/swift/) and look for 'tempurl' in the proxy server pipeline or middleware configurationAffected if The tempurl middleware is present and enabled in the proxy server configuration
-
Confirm DLO functionality is availableCheck if the object-server configuration allows DLO operations; verify the 'dlo' middleware or container-based segment handling is configuredAffected if DLO (Dynamic Large Object) functionality is enabled and the system can process manifest files referencing multiple segments
-
Assess cross-container access exposureReview tempurl permissions and container ACLs to determine if PUT tempurl for one container can reference objects in a different containerAffected if A valid PUT tempurl for one container can be used to create a manifest pointing to objects in another container the user should not access
A user is affected if running OpenStack Swift version 2.3.0 or earlier AND tempurl middleware is enabled, allowing cross-container DLO manifest creation.
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 OpenStack Swift to version 2.4.0 or later. If immediate upgrade is not possible, review and restrict tempurl permissions and cross-container access controls.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5223 — 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-2015-5223 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