# CVE-2014-0644: XML external entity in n/a

> Remote attackers can read arbitrary files, including sensitive system files, via XML External Entity injection in the login API.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p2xc-mcp4-pvvr

## What is CVE-2014-0644?

CVE-2014-0644 is a high-severity vulnerability in n/a, published on 17 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC Cloud Tiering Appliance (CTA) 10 through SP1 allows remote attackers to read arbitrary files via an api/login request containing an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, as demonstrated by reading the /etc/shadow file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Emc Cloud Tiering Appliance, Emc Cloud Tiering Appliance Software.

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

No fix has been published for CVE-2014-0644 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-0644 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-0644 exists.

Public exploit code:

- EMC Cloud Tiering Appliance 10.0 - XML External Entity Arbitrary File Read (Metasploit) (exploitdb)
- EMC CTA v10.0 Unauthenticated XXE Arbitrary File Read (metasploit)

## Other vulnerabilities in n/a

- [CVE-2012-2285](https://insights.sbomify.com/CVE-2012-2285/): Auth bypass in n/a (medium 6.8)
- [CVE-2014-0645](https://insights.sbomify.com/CVE-2014-0645/): Weak cryptography in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0644 is a high-severity vulnerability in n/a, published on 17 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-0644 exists.

Affected product: n/a. 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-0644/ (Markdown: https://insights.sbomify.com/CVE-2014-0644/index.md)
```

## Sources

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

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