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

> Authenticated attackers can read arbitrary files via XML External Entity injection in the Openbravo ERP XML API.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2gjx-c22x-h568

## What is CVE-2013-3617?

CVE-2013-3617 is a low-severity vulnerability in n/a, published on 2 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The XML API in Openbravo ERP 2.5, 3.0, and earlier allows remote authenticated users to read arbitrary files via an XML document with an external entity declaration in conjunction with an entity reference to /ws/dal/ADUser or other /ws/dal/XXX interfaces, related to an XML External Entity (XXE) issue.

Weakness: CWE-264

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

It affects 1 product.


Products: Openbravo Openbravo Erp.

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

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

## Is CVE-2013-3617 being exploited?

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

Public exploit code:

- Openbravo ERP - XML External Entity Information Disclosure (exploitdb)
- Openbravo ERP XXE Arbitrary File Read (metasploit)

## Other vulnerabilities in n/a

- [CVE-2017-9437](https://insights.sbomify.com/CVE-2017-9437/): SQL injection in n/a (high 8.8)
- [CVE-2019-14362](https://insights.sbomify.com/CVE-2019-14362/): Path traversal in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3617 is a low-severity vulnerability in n/a, published on 2 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3617 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-3617/ (Markdown: https://insights.sbomify.com/CVE-2013-3617/index.md)
```

## Sources

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

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