# CVE-2020-25713: Memory corruption in raptor2

> A malformed input file causes a segmentation fault in the Raptor2 library, leading to a denial of service condition.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-25713, DLA-2846-1, GHSA-5m9f-jxr5-6jv9, MGASA-2020-0431, OESA-2022-1796, SUSE-SU-2022:2895-1, SUSE-SU-2022:2896-1, UBUNTU-CVE-2020-25713

## What is CVE-2020-25713?

CVE-2020-25713 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 13 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A malformed input file can lead to a segfault due to an out of bounds array access in raptor_xml_writer_start_element_common.

Weakness: CWE-125 (Out-of-bounds Read), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-25713?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `raptor` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP3 | All versions | 2.0.15-150200.9.12.1 |
| `raptor` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 2.0.15-150200.9.12.1 |
| `raptor` | SUSE:Linux Enterprise Module for Package Hub 15 SP3 | All versions | 2.0.15-150200.9.12.1 |
| `raptor` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.0.15-5.6.1 |
| `raptor` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.0.15-5.6.1 |
| `raptor` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.0.15-5.6.1 |
| `raptor` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 2.0.15-5.6.1 |
| `raptor` | openSUSE:Leap 15.3 | All versions | 2.0.15-150200.9.12.1 |
| `raptor` | openSUSE:Leap 15.4 | All versions | 2.0.15-150200.9.12.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Librdf Raptor Rdf Syntax Library.

## How do I fix CVE-2020-25713?

Apply the vendor's patch.

## Is CVE-2020-25713 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25713 and fix it if it is affected.

What it is: CVE-2020-25713 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 13 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25713 in the wild and no public exploit code.

Affected product: Debian Debian 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-2020-25713/ (Markdown: https://insights.sbomify.com/CVE-2020-25713/index.md)
```

## Sources

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

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