# CVE-2011-0433: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted AFM files in DVI documents processed by t1lib.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-37048, AZL-7377, DEBIAN-CVE-2011-0433, GHSA-m37c-h529-2gqw

## What is CVE-2011-0433?

CVE-2011-0433 is a medium-severity memory corruption vulnerability in n/a, published on 19 Nov 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the linetoken function in afmparse.c in t1lib, as used in teTeX 3.0.x, GNOME evince, and possibly other products, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a DVI file containing a crafted Adobe Font Metrics (AFM) file, a different vulnerability than CVE-2010-2642.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2011-0433?

It affects 3 products.


Products: Gnome Evince, T1lib T1lib, Tetex Tetex.

## How do I fix CVE-2011-0433?

Upgrade to a fixed version.

## Is CVE-2011-0433 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1000159](https://insights.sbomify.com/CVE-2017-1000159/): Command injection in n/a (high 7.8)
- [CVE-2011-5244](https://insights.sbomify.com/CVE-2011-5244/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0433 and fix it if it is affected.

What it is: CVE-2011-0433 is a medium-severity memory corruption vulnerability in n/a, published on 19 Nov 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-0433 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-2011-0433/ (Markdown: https://insights.sbomify.com/CVE-2011-0433/index.md)
```

## Sources

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

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