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

> A flaw in Wireshark's ASN.1 BER dissector allows attackers to crash the application via crafted packets, requiring an upgrade to fix.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-13619, GHSA-mh9j-54rp-3h7j, MGASA-2019-0227, SUSE-SU-2019:2103-1, SUSE-SU-2019:2104-1, UBUNTU-CVE-2019-13619, openSUSE-SU-2019:1965-1

## What is CVE-2019-13619?

CVE-2019-13619 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 17 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Wireshark 3.0.0 to 3.0.2, 2.6.0 to 2.6.9, and 2.4.0 to 2.4.15, the ASN.1 BER dissector and related dissectors could crash. This was addressed in epan/asn1.c by properly restricting buffer increments.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireshark` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2.4.16-48.51.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.4.16-3.31.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 2.4.16-3.31.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 2.4.16-3.31.1 |
| `wireshark` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 2.4.16-3.31.1 |
| `wireshark` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 2.4.16-48.51.1 |
| `wireshark` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2.4.16-48.51.1 |
| `wireshark` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 2.4.16-48.51.1 |
| `wireshark` | openSUSE:Leap 15.0 | All versions | 2.4.16-lp151.2.6.1 |
| `wireshark` | openSUSE:Leap 15.1 | All versions | 2.4.16-lp151.2.6.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Opensuse Leap, Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2019-13619 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13619 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, published on 17 Jul 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-13619 in the wild and no public exploit code.

Affected product: Canonical Ubuntu 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-13619/ (Markdown: https://insights.sbomify.com/CVE-2019-13619/index.md)
```

## Sources

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

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