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

> A buffer overflow in OpenConnect allows a malicious server to execute arbitrary code or cause denial of service via crafted HTTP chunked encoding.

- **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:** 17 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-16239, DLA-1945-1, DSA-4607-1, GHSA-j5c8-5345-567f, MGASA-2020-0005, SUSE-SU-2019:2737-1, SUSE-SU-2019:2744-1, SUSE-SU-2019:2744-2, UBUNTU-CVE-2019-16239, USN-4565-1, openSUSE-SU-2019:2385-1, openSUSE-SU-2019:2388-1, openSUSE-SU-2024:13322-1

## What is CVE-2019-16239?

CVE-2019-16239 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

process_http_response in OpenConnect before 8.05 has a Buffer Overflow when a malicious server uses HTTP chunked encoding with crafted chunk sizes.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openconnect` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 7.08-3.4.1 |
| `openconnect` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 7.08-3.4.1 |
| `openconnect` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 7.08-3.4.1 |
| `openconnect` | SUSE:Linux Enterprise Workstation Extension 15 | All versions | 7.08-6.3.1 |
| `openconnect` | SUSE:Linux Enterprise Workstation Extension 15 SP1 | All versions | 7.08-6.3.1 |
| `openconnect` | openSUSE:Leap 15.0 | All versions | 7.08-lp150.5.3.1 |
| `openconnect` | openSUSE:Leap 15.1 | All versions | 7.08-lp151.6.3.1 |

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

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

Upgrade to a fixed version.

## Is CVE-2019-16239 being exploited?

There is no known exploitation of CVE-2019-16239 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-16239 and fix it if it is affected.

What it is: CVE-2019-16239 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 17 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-16239 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-16239/ (Markdown: https://insights.sbomify.com/CVE-2019-16239/index.md)
```

## Sources

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

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