# CVE-2012-2997: XML external entity in n/a

> Authenticated remote attackers can read arbitrary files on F5 BIG-IP systems via XML External Entity injection in the admin interface.

- **Severity:** Medium 4.0 (`AV:N/AC:L/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:** 21 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pfqw-9w76-j32f

## What is CVE-2012-2997?

CVE-2012-2997 is a medium-severity vulnerability in n/a, published on 21 Jan 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

XML External Entity (XXE) vulnerability in sam/admin/vpe2/public/php/server.php in F5 BIG-IP 10.0.0 through 10.2.4 and 11.0.0 through 11.2.1 allows remote authenticated users to read arbitrary files via a crafted XML file.

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

## Which versions are affected by CVE-2012-2997?

It affects 1 product.


Products: F5 Big-Ip Configuration Utility.

## How do I fix CVE-2012-2997?

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

## Is CVE-2012-2997 being exploited?

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

Public exploit code:

- F5 Networks BIG-IP - XML External Entity Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2997 and fix it if it is affected.

What it is: CVE-2012-2997 is a medium-severity vulnerability in n/a, published on 21 Jan 2014. 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-2012-2997 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-2012-2997/ (Markdown: https://insights.sbomify.com/CVE-2012-2997/index.md)
```

## Sources

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

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