# CVE-2016-9181: XML external entity in n/a

> An attacker can cause denial of service or information disclosure by crafting a malicious SVG file processed by the Perl Image-Info library.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-9181, GHSA-99g7-5p97-g9vw, MGASA-2017-0151, UBUNTU-CVE-2016-9181

## What is CVE-2016-9181?

CVE-2016-9181 is a high-severity vulnerability in n/a, published on 22 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

perl-Image-Info: When parsing an SVG file, external entity expansion (XXE) was not disabled. An attacker could craft an SVG file which, when processed by an application using perl-Image-Info, could cause denial of service or, potentially, information disclosure.

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

## Which versions are affected by CVE-2016-9181?

It affects 1 product.


Products: Image-Info Project Image-Info for Perl.

## How do I fix CVE-2016-9181?

Apply the vendor's patch.

## Is CVE-2016-9181 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9181 and fix it if it is affected.

What it is: CVE-2016-9181 is a high-severity vulnerability in n/a, published on 22 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-9181 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-2016-9181/ (Markdown: https://insights.sbomify.com/CVE-2016-9181/index.md)
```

## Sources

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

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