# CVE-2015-6463: XML external entity in n/a

> Remote attackers can read arbitrary files, access intranet servers, or cause denial of service via XML External Entity injection in HART Comm DTM components.

- **Severity:** Medium 5.8 (`AV:A/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:** 28 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p38c-mvc3-4j96

## What is CVE-2015-6463?

CVE-2015-6463 is a medium-severity vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CodeWrights HART Comm DTM components, as used with Endress+Hauser FieldCare, allow remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service (CPU and memory consumption) via a longtag XML schema 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-2015-6463?

It affects 2 products.


Products: Codewrights Hart Comm Dtm, Endress\+hauser Hart Comm Dtm.

## How do I fix CVE-2015-6463?

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

## Is CVE-2015-6463 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6463 and fix it if it is affected.

What it is: CVE-2015-6463 is a medium-severity vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6463 in the wild and no public exploit code.

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-2015-6463/ (Markdown: https://insights.sbomify.com/CVE-2015-6463/index.md)
```

## Sources

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

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