LiveActive security incident?Get immediate response
CVE Record

CVE-2019-3822: libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow.

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable curl/libcurl client can crash or be corrupted when it authenticates with NTLM to a malicious or faulty HTTP server. The business risk is disruption of systems that rely on curl-based outbound HTTP connections, especially automated services using older OS packages or embedded vendor appliances.

Executive priority

Treat this as a high-priority patching issue for systems using older curl/libcurl, especially automated infrastructure and vendor products. Urgency is lower where NTLM is not used, but broad libcurl reuse makes inventory important.

Technical view

CVE-2019-3822 is a stack-based buffer overflow in libcurl 7.36.0 through versions before 7.64.0. The NTLM type-3 header creation path uses an incorrect unsigned arithmetic bounds check, allowing oversized NTLMv2 response data from a prior server header to exceed a local buffer.

Likely exposure

Exposure is most likely where applications, scripts, agents, containers, appliances, or OS packages include vulnerable libcurl and perform HTTP NTLM authentication. Systems that never use NTLM authentication are less likely to be practically exposed, but version inventory is still required.

Exploitation context

The source bundle does not identify CISA KEV listing or active exploitation. The scenario requires a client using vulnerable libcurl to process large NTLMv2 response data from a malicious or broken HTTP server before generating the outgoing NTLM type-3 header.

Researcher notes

The key exposure condition is the NTLM authentication code path in Curl_auth_create_ntlm_type3_message. Source evidence supports integrity and availability impact, with CVSS 7.1 and CWE-121. No exploit-in-the-wild claim is supported by the provided bundle.

Mitigation direction

  • Upgrade curl/libcurl using the relevant OS or vendor advisory guidance.
  • Prioritize systems using HTTP NTLM authentication or connecting to untrusted servers.
  • Refresh container base images and embedded runtime images that package libcurl.
  • Consult vendor advisories for bundled third-party product exposure and fixes.
  • If immediate upgrade is unavailable, review vendor guidance for supported compensating controls.

Validation and detection

  • Inventory installed curl and libcurl versions across hosts, images, and appliances.
  • Confirm whether applications use libcurl for HTTP NTLM authentication.
  • Check package manager advisories from Debian, Ubuntu, Gentoo, Red Hat, or applicable vendors.
  • Review SBOMs and container base images for vulnerable libcurl ranges.
  • After patching, verify runtime-linked libcurl versions, not only package metadata.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-3822 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
15Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.1High
CVSS 3.0 vector shape for CVE-2019-3822Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The curl Projectcurl7.64.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.