# CVE-2019-17362: Information disclosure in n/a

> Attackers can cause denial of service or read sensitive memory via crafted DER data in LibTomCrypt due to improper UTF-8 validation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 9 Oct 2019
- **Updated:** 15 Nov 2024
- **Also known as:** ALPINE-CVE-2019-17362, AZL-36958, AZL-7275, DEBIAN-CVE-2019-17362, DLA-1951-1, GHSA-x32c-6j92-4hp9, MGASA-2020-0028, OESA-2021-1029, SUSE-SU-2019:2808-1, SUSE-SU-2019:3095-1, UBUNTU-CVE-2019-17362, USN-4868-1, openSUSE-SU-2019:2454-1, openSUSE-SU-2019:2514-1

## What is CVE-2019-17362?

CVE-2019-17362 is a critical vulnerability in Debian Debian Linux, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In LibTomCrypt through 1.18.2, the der_decode_utf8_string function (in der_decode_utf8_string.c) does not properly detect certain invalid UTF-8 sequences. This allows context-dependent attackers to cause a denial of service (out-of-bounds read and crash) or read information from other memory locations via carefully crafted DER-encoded data.

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

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libtomcrypt` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.17-3.3.1 |
| `libtomcrypt` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 1.17-3.3.1 |
| `libtomcrypt` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 1.17-3.3.1 |
| `libtomcrypt` | openSUSE:Leap 15.0 | All versions | 1.17-lp150.2.3.1 |
| `libtomcrypt` | openSUSE:Leap 15.1 | All versions | 1.17-lp151.3.3.1 |

Products: Debian Debian Linux, Libtom Libtomcrypt.

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

Apply the vendor's patch.

## Is CVE-2019-17362 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17362 exists.

## 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-2019-17362 and fix it if it is affected.

What it is: CVE-2019-17362 is a critical vulnerability in Debian Debian Linux, published on 9 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17362 exists.

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-2019-17362/ (Markdown: https://insights.sbomify.com/CVE-2019-17362/index.md)
```

## Sources

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

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