# CVE-2013-5452: IBM FileNet Business Process Framework 4.1.0 allows remote authenticated users to read arbitrary files or send TCP requests to intranet serv


- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5w5v-4mrp-h63j

## What is CVE-2013-5452?

CVE-2013-5452 is a low-severity vulnerability in n/a, published on 19 Dec 2013. 

### Official description

IBM FileNet Business Process Framework 4.1.0 allows remote authenticated users to read arbitrary files or send TCP requests to intranet servers via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

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

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

It affects 1 product.


Products: Ibm Filenet Business Process Framework.

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

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

## Is CVE-2013-5452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5452 is a low-severity vulnerability in n/a, published on 19 Dec 2013. 
Exploitation: There is no known exploitation of CVE-2013-5452 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-2013-5452/ (Markdown: https://insights.sbomify.com/CVE-2013-5452/index.md)
```

## Sources

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

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