# CVE-2013-1591: Integer overflow in n/a

> An integer overflow in the Pixman library can cause a stack-based buffer overflow and infinite loop, potentially leading to denial of service or code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1591, GHSA-7rw2-cfj2-g8vr, RHSA-2013:0687

## What is CVE-2013-1591?

CVE-2013-1591 is a critical vulnerability in Redhat Enterprise Linux, published on 31 Jan 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has unspecified impact and context-dependent attack vectors.  NOTE: this issue might be resultant from an integer overflow in the fast_composite_scaled_bilinear function in pixman-inlines.h, which triggers an infinite loop.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pixman` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26.2-5.el6_4 |
| `pixman-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26.2-5.el6_4 |
| `pixman-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.26.2-5.el6_4 |
| `pixman` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26.2-5.el6_4 |
| `pixman-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26.2-5.el6_4 |
| `pixman-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.26.2-5.el6_4 |
| `pixman` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26.2-5.el6_4 |
| `pixman-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26.2-5.el6_4 |
| `pixman-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.26.2-5.el6_4 |
| `pixman` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26.2-5.el6_4 |
| `pixman-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26.2-5.el6_4 |
| `pixman-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.26.2-5.el6_4 |

Products: Palemoon Pale Moon, Redhat Enterprise Linux, Redhat Enterprise Virtualization.

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

Upgrade to a fixed version.

## Is CVE-2013-1591 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-12292](https://insights.sbomify.com/CVE-2018-12292/): Use after free in n/a (critical 9.8)
- [CVE-2020-9545](https://insights.sbomify.com/CVE-2020-9545/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1591 is a critical vulnerability in Redhat Enterprise Linux, published on 31 Jan 2013. 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-1591 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-1591/ (Markdown: https://insights.sbomify.com/CVE-2013-1591/index.md)
```

## Sources

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

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