# CVE-2019-17040: Memory corruption in n/a

> An out-of-bounds access in Rsyslog's pmdb2diag module allows attackers to cause denial of service or potentially execute arbitrary code.

- **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:** 30 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2019-17040, DEBIAN-CVE-2019-17040, GHSA-8xrx-4ww5-fhx5

## What is CVE-2019-17040?

CVE-2019-17040 is a critical memory corruption vulnerability in n/a, published on 30 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Rsyslog Rsyslog.

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

Upgrade to a fixed version.

## Is CVE-2019-17040 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-12588](https://insights.sbomify.com/CVE-2017-12588/): Other in n/a (critical 9.8)
- [CVE-2008-5617](https://insights.sbomify.com/CVE-2008-5617/): Auth bypass in n/a (high 8.5)
- [CVE-2014-3634](https://insights.sbomify.com/CVE-2014-3634/): Memory corruption in n/a (high 7.5)
- [CVE-2013-4758](https://insights.sbomify.com/CVE-2013-4758/): Use after free in n/a (medium 6.8)
- [CVE-2015-3243](https://insights.sbomify.com/CVE-2015-3243/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17040 is a critical memory corruption vulnerability in n/a, published on 30 Sep 2019. 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-2019-17040 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-17040/ (Markdown: https://insights.sbomify.com/CVE-2019-17040/index.md)
```

## Sources

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

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