CVE-2015-1195
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 V2 API in OpenStack Image Registry and Delivery Service (Glance) before 2014.1.4 and 2014.2.x before 2014.2.2 allows remote authenticated users to read or delete arbitrary files via a full pathname in a filesystem: URL in the image location property. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-9493.
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 V2 API in OpenStack Glance contains a path traversal vulnerability allowing authenticated users to read or delete arbitrary files by providing a full pathname in a filesystem: URL within the image location property. This is an incomplete fix for the prior CVE-2014-9493, indicating the original patch did not fully address path validation in the V2 API image location handling.
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>= 2014.1, < 2014.1.4>= 2014.2, < 2014.2.2CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Determine installed Glance versionRun the command to check the installed Glance package version (e.g., glance --version, rpm -q glance, pip show glance, or check /var/log/glance for version indicators)Affected if The version is 2014.1.x before 2014.1.4, or 2014.2.x before 2014.2.2, indicating the patch is not applied
-
Verify V2 API is accessibleCheck if the Glance V2 API endpoint is exposed by reviewing the service configuration (e.g., glance-api.conf pipeline settings, or attempt a request to /v2/images)Affected if The V2 API endpoint is enabled and reachable, allowing the vulnerable code path to be exercised
-
Confirm user authentication is possibleVerify that user authentication to Glance is configured (check keystone integration, token validation settings in glance-api.conf)Affected if Non-admin or non-privileged users can authenticate to Glance, enabling them to exploit the path traversal via image location property
-
Review filesystem: URL handling in image locationsInspect the image location configuration or attempt to create an image with a filesystem: URL containing path traversal sequences (e.g., ../../) to observe if validation is presentAffected if The system accepts filesystem: URLs with path traversal patterns in the image location property without rejecting them, indicating the vulnerability is present
If the Glance version falls within the affected ranges (2014.1.x < 2014.1.4 or 2014.2.x < 2014.2.2), the V2 API is enabled, and users can authenticate, the environment is likely vulnerable to path traversal via filesystem: URLs in image locations.
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 data2014.1.42014.2.2
Upgrade Glance to version 2014.1.4 or later for the Juno series, or 2014.2.2 or later for the Kilo series to obtain the complete fix. Implement strict validation of filesystem: URLs to prevent path traversal attacks.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1195 — 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-1195 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