# CVE-2013-0340: XML external entity in apple:ipados

> Remote attackers can cause denial of service, access intranet servers, or read arbitrary files via crafted XML documents in the expat library.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** Yes
- **Published:** 21 Jan 2014
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2013-0340, GHSA-w3v2-46wf-pq33, OESA-2021-1261, PSF-2014-1, RHBA-2022:8290

## What is CVE-2013-0340?

CVE-2013-0340 is a medium-severity vulnerability in Apple Ipados, published on 21 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

expat before version 2.4.0 does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue.  NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `expat-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.4.9-1.el9_1 |
| `expat-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.4.9-1.el9_1 |
| `expat-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.4.9-1.el9_1 |
| `expat` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.4.9-1.el9_1 |
| `expat-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.4.9-1.el9_1 |
| `expat-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.4.9-1.el9_1 |

Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Tvos, Apple Watchos, Libexpat Project Libexpat, Python Python.

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

Upgrade to a fixed version.

## Is CVE-2013-0340 being exploited?

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

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0340 is a medium-severity vulnerability in Apple Ipados, published on 21 Jan 2014. 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-2013-0340 in the wild and no public exploit code.

Affected product: Apple Ipados. 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-0340/ (Markdown: https://insights.sbomify.com/CVE-2013-0340/index.md)
```

## Sources

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

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