# CVE-2014-9493: Path traversal in n/a

> Authenticated users can read or delete arbitrary files via path traversal in the image location property of OpenStack Glance.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9493, GHSA-jgr4-76hh-5p7q, RHSA-2015:0246

## What is CVE-2014-9493?

CVE-2014-9493 is a medium-severity path traversal vulnerability in Redhat Openstack, published on 7 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The V2 API in OpenStack Image Registry and Delivery Service (Glance) before 2014.2.2 and 2014.1.4 allows remote authenticated users to read or delete arbitrary files via a full pathname in a file: URL in the image location property.

Weakness: CWE-264

## Which versions are affected by CVE-2014-9493?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-glance` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-3.el6ost |
| `openstack-glance-doc` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-3.el6ost |
| `python-glance` | Red Hat:openstack:4::el6 | All versions | 0:2013.2.4-3.el6ost |
| `openstack-glance` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.3-4.el6ost |
| `openstack-glance-doc` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.3-4.el6ost |
| `python-glance` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.3-4.el6ost |
| `openstack-glance` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.3-4.el7ost |
| `openstack-glance-doc` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.3-4.el7ost |
| `python-glance` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.3-4.el7ost |

Products: Openstack Image Registry and Delivery Service \(Glance\), Redhat Openstack.

## How do I fix CVE-2014-9493?

Upgrade to a fixed version.

## Is CVE-2014-9493 being exploited?

There is no known exploitation of CVE-2014-9493 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Openstack

- [CVE-2015-5286](https://insights.sbomify.com/CVE-2015-5286/): OpenStack Image Service (Glance) allows remote authenticated users to bypass storage quota, cause denial of service (medium 6.8)
- [CVE-2015-1195](https://insights.sbomify.com/CVE-2015-1195/): OpenStack Glance v2 API unrestricted path traversal through filesystem:// scheme (medium 6.5)
- [CVE-2015-5251](https://insights.sbomify.com/CVE-2015-5251/): OpenStack Image Service (Glance) allows remote authenticated users to bypass access restrictions (medium 5.5)
- [CVE-2016-0757](https://insights.sbomify.com/CVE-2016-0757/): OpenStack Image Service (Glance) vulnerable to Improper Access Control (medium 4.3)
- [CVE-2014-9684](https://insights.sbomify.com/CVE-2014-9684/): OpenStack Glance Denial of service by creating a large number of images (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9493 and fix it if it is affected.

What it is: CVE-2014-9493 is a medium-severity path traversal vulnerability in Redhat Openstack, published on 7 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9493 in the wild and no public exploit code.

Affected product: Redhat Openstack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-9493/ (Markdown: https://insights.sbomify.com/CVE-2014-9493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-9493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-9493
- OSV: https://osv.dev/vulnerability/CVE-2014-9493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-9493/
Summaries are generated and may contain mistakes; the official description above is the record.