# CVE-2013-5014: XML external entity in n/a

> Remote attackers can read arbitrary files from the Symantec Endpoint Protection Manager management console via XML External Entity injection.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-44qm-5mf2-4vv3

## What is CVE-2013-5014?

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

### Official description

The management console in Symantec Endpoint Protection Manager (SEPM) 11.0 before 11.0.7405.1424 and 12.1 before 12.1.4023.4080, and Symantec Protection Center Small Business Edition 12.x before 12.1.4023.4080, allows remote attackers to read arbitrary files via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

## Which versions are affected by CVE-2013-5014?

It affects 2 products.


Products: Symantec Endpoint Protection Manager, Symantec Protection Center.

## How do I fix CVE-2013-5014?

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

## Is CVE-2013-5014 being exploited?

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

Public exploit code:

- Symantec Endpoint Protection Manager 11.0/12.0/12.1 - Remote Command Execution (exploitdb)
- Symantec Endpoint Protection Manager /servlet/ConsoleServlet Remote Command Execution (metasploit)
- Symantec Endpoint Protection Manager - Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-3648](https://insights.sbomify.com/CVE-2016-3648/): Security feature bypass in n/a (high 8.8)
- [CVE-2016-3650](https://insights.sbomify.com/CVE-2016-3650/): Information disclosure in n/a (high 8.8)
- [CVE-2015-8153](https://insights.sbomify.com/CVE-2015-8153/): SQL injection in n/a (high 8.8)
- [CVE-2015-8154](https://insights.sbomify.com/CVE-2015-8154/): Privilege escalation in n/a (high 8.8)
- [CVE-2015-6555](https://insights.sbomify.com/CVE-2015-6555/): Code injection in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5014 and fix it if it is affected.

What it is: CVE-2013-5014 is a high-severity vulnerability in n/a, published on 14 Feb 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-2013-5014 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-2013-5014/ (Markdown: https://insights.sbomify.com/CVE-2013-5014/index.md)
```

## Sources

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

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