# CVE-2019-3822: Memory corruption in curl

> A stack-based buffer overflow in libcurl's NTLM authentication allows remote attackers to execute arbitrary code or cause denial of service via malicious server responses.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Feb 2019
- **Updated:** 15 Apr 2026
- **Also known as:** ALPINE-CVE-2019-3822, CLEANSTART-2026-IB97779, CURL-CVE-2019-3822, DEBIAN-CVE-2019-3822, GHSA-8wr2-mqj7-7vxp, UBUNTU-CVE-2019-3822

## What is CVE-2019-3822?

CVE-2019-3822 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (`lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()`), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 16 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Haxx Libcurl, Netapp Active Iq Unified Manager, Netapp Clustered Data Ontap, Netapp Oncommand Insight, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Oracle Communications Operations Monitor, Oracle Enterprise Manager Ops Center, Oracle Http Server, Oracle Mysql Server, Oracle Secure Global Desktop, Oracle Services Tools Bundle, Redhat Enterprise Linux, Siemens Sinema Remote Connect Client.

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

Upgrade to a fixed version.

## Is CVE-2019-3822 being exploited?

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

What it is: CVE-2019-3822 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3822 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-3822/ (Markdown: https://insights.sbomify.com/CVE-2019-3822/index.md)
```

## Sources

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

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