# CVE-2019-6462: Denial of service in n/a

> An infinite loop in the Cairo graphics library allows attackers to cause a denial of service via crafted input.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** 16 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-6462, DEBIAN-CVE-2019-6462, ECHO-cf8c-c1d6-f73d, GHSA-7m29-23h6-ccwp, JLSEC-2025-16, MGASA-2021-0497, ROOT-OS-DEBIAN-12-CVE-2019-6462, SUSE-SU-2021:3502-1, SUSE-SU-2024:1704-1, SUSE-SU-2024:1704-2, SUSE-SU-2025:02795-1, UBUNTU-CVE-2019-6462

## What is CVE-2019-6462?

CVE-2019-6462 is a medium-severity denial of service vulnerability in n/a, published on 16 Jan 2019. 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

An issue was discovered in cairo 1.16.0. There is an infinite loop in the function _arc_error_normalized in the file cairo-arc.c, related to _arc_max_angle_for_tolerance_normalized.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2019-6462?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cairo` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.16.0-150200.5.5.1 |
| `cairo` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.15.2-25.6.2 |
| `cairo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.15.2-25.6.2 |
| `cairo` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.15.2-25.6.2 |
| `cairo` | openSUSE:Leap 15.5 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | openSUSE:Leap Micro 5.3 | All versions | 1.16.0-150400.11.3.1 |
| `cairo` | openSUSE:Leap Micro 5.4 | All versions | 1.16.0-150400.11.3.1 |

Products: Cairographics Cairo.

## How do I fix CVE-2019-6462?

Apply the vendor's patch.

## Is CVE-2019-6462 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35492](https://insights.sbomify.com/CVE-2020-35492/): Memory corruption in cairo (high 7.8)
- [CVE-2017-9814](https://insights.sbomify.com/CVE-2017-9814/): Denial of service in n/a (high 7.5)
- [CVE-2016-3190](https://insights.sbomify.com/CVE-2016-3190/): Denial of service in n/a (high 7.5)
- [CVE-2019-6461](https://insights.sbomify.com/CVE-2019-6461/): Denial of service in n/a (medium 6.5)
- [CVE-2018-19876](https://insights.sbomify.com/CVE-2018-19876/): Use after free in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6462 and fix it if it is affected.

What it is: CVE-2019-6462 is a medium-severity denial of service vulnerability in n/a, published on 16 Jan 2019. 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-2019-6462 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-2019-6462/ (Markdown: https://insights.sbomify.com/CVE-2019-6462/index.md)
```

## Sources

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

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