CVE-2019-3822

CRITICALNVD 9.89.8Trending — 4 sources updated this weekElevated

Also known asEUVD-2019-13445 (ENISA EUVD) · GHSA-8wr2-mqj7-7vxp (GitHub Security Advisories)Source: ENISA EUVD

9.8EG

EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).

High severity, but no confirmed exploitation yet

CISA-KEV: Not listedEPSS PROB: 13%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3: 9.8
EG Score: 9.8CRITICALmedium confidence
EG Risk: 60
EPSS PROB: 13%
EPSS %ILE: 96th
KEV: Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity: 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood: 13% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation: None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority: SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 6, 2019

Last Modified

November 21, 2024

Advisory Details (10)

Auto-updated Oct 5, 2026

Patch available. Sources: redhat.

Web page

myF5

https://support.f5.com/csp/article/K84141449

Web page

NetApp Product Security

https://security.netapp.com/advisory/ntap-20190719-0004/

Web page

NetApp Product Security

https://security.netapp.com/advisory/ntap-20190315-0001/

Web page

cURL: Multiple vulnerabilities (GLSA 201903-03) — Gentoo security

https://security.gentoo.org/glsa/201903-03

Web page

Pony Mail

https://lists.apache.org/thread.html/8338a0f605bdbb3a6098bb76f666a95fc2b2f53f37fa1ecc89f1146f%40%3Cdevnull.infra.apache.org%3E

Web page

curl - NTLMv2 type-3 header stack buffer overflow - CVE-2019-3822

https://curl.haxx.se/docs/CVE-2019-3822.html

Web page

https://cert-portal.siemens.com/productcert/pdf/ssa-436177.pdf

Red HatMentions a patch (unverified)

1670254 – (CVE-2019-3822) CVE-2019-3822 curl: NTLMv2 type-3 header stack buffer overflow

Affected: Red Hat Enterprise Linux 5, 6, and 7 do not support NTLMv2 type-3 headers, hence they are not affected by this flaw.

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3822

Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2019:3701

Web page

CVE-2019-3822 - PSIRT.COM

http://www.securityfocus.com/bid/106950

Vendor Advisories for CVE-2019-3822(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

RHSA-2019:1543
Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.29 SP2 security update

Patch Availability(3)

Vendor / Ecosystem	Fix (by version range) / Patch	Released	Source
ubuntu	libcurl4-openssl-dev (7.47.0-1ubuntu2.12) @ xenial	2026-11-02	ubuntu
redhat	curl-0:7.61.1-11.el8	2019-11-05	redhat
redhat	patch	2019-06-18	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(25 across 25 ecosystems)

Alpine:v3.10(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.11(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.12(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.13(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.14(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.15(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.16(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.17(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.18(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.19(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.20(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.21(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.22(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.23(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.24(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Alpine:v3.6(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.61.1-r2: fixed in 7.61.1-r2	—

Alpine:v3.7(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.61.1-r2: fixed in 7.61.1-r2	—

Alpine:v3.8(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.61.1-r2: fixed in 7.61.1-r2	—

Alpine:v3.9(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-r0: fixed in 7.64.0-r0	—

Debian:11(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-1: fixed in 7.64.0-1	—

Debian:12(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-1: fixed in 7.64.0-1	—

Debian:13(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-1: fixed in 7.64.0-1	—

Debian:14(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	—	every version up to 7.64.0-1: fixed in 7.64.0-1	—

Debian:8(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	7.38.0-4 ... 7.38.0-4+deb8u9 (14 versions)	every version up to 7.38.0-4+deb8u14: fixed in 7.38.0-4+deb8u14	—

Debian:9(1)

Package	Vulnerable range	Fix by version range	Dependents
curl	7.52.1-5 ... 7.52.1-5+deb9u8 (9 versions)	every version up to 7.52.1-5+deb9u9: fixed in 7.52.1-5+deb9u9	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 27× in last 7d / 91× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 231 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

2026-11-02 10:45 UTCEG score recompute
2026-11-02 10:45 UTCVendor advisory
2026-11-02 10:45 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-11-01 10:36 UTCEG score recompute
2026-11-01 10:36 UTCVendor advisory
2026-11-01 10:36 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-31 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-31 10:26 UTCEG score recompute
2026-10-31 10:26 UTCVendor advisory
2026-10-31 10:26 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-30 16:29 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-30 10:16 UTCEG score recompute
2026-10-30 10:16 UTCVendor advisory
2026-10-30 10:16 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-29 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-29 10:06 UTCEG score recompute
2026-10-29 10:06 UTCVendor advisory
2026-10-29 10:06 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-28 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-28 09:56 UTCEG score recompute
2026-10-28 09:56 UTCVendor advisory
2026-10-28 09:56 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-27 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-27 08:54 UTCEG score recompute
2026-10-27 08:54 UTCVendor advisory

Show 75 more

2026-10-27 08:54 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-26 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-26 07:16 UTCVendor advisory
2026-10-26 07:16 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-25 18:58 UTCEG score recompute
2026-10-25 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-25 07:04 UTCEG score recompute
2026-10-25 07:04 UTCVendor advisory
2026-10-25 07:04 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-24 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-24 06:53 UTCEG score recompute
2026-10-24 06:53 UTCVendor advisory
2026-10-24 06:53 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-23 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-23 06:43 UTCEG score recompute
2026-10-23 06:43 UTCVendor advisory
2026-10-23 06:43 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-22 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-22 06:32 UTCEG score recompute
2026-10-22 06:32 UTCVendor advisory
2026-10-22 06:32 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-21 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-21 06:17 UTCEG score recompute
2026-10-21 06:17 UTCVendor advisory
2026-10-21 06:17 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-20 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-20 06:07 UTCEG score recompute
2026-10-20 06:07 UTCVendor advisory
2026-10-20 06:07 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-19 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-19 05:56 UTCEG score recompute
2026-10-19 05:56 UTCVendor advisory
2026-10-19 05:56 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-18 05:44 UTCEG score recompute
2026-10-18 05:44 UTCVendor advisory
2026-10-18 05:44 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-17 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-17 05:32 UTCEG score recompute
2026-10-17 05:32 UTCVendor advisory
2026-10-17 05:32 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-16 16:32 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-16 05:19 UTCEG score recompute
2026-10-16 05:19 UTCVendor advisory
2026-10-16 05:19 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-15 16:27 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-15 03:45 UTCEG score recompute
2026-10-15 03:45 UTCVendor advisory
2026-10-15 03:45 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-14 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-13 23:50 UTCEG score recompute
2026-10-13 23:50 UTCVendor advisory
2026-10-13 23:50 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-13 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-12 19:55 UTCVendor advisory
2026-10-12 19:55 UTCGHSA enrichmentGHSA-8wr2-mqj7-7vxp · GitHub severity CRITICAL · GitHub CVSS 9.8
2026-10-12 19:54 UTCEG score recompute
2026-10-12 16:28 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-12 00:18 UTCEG score recompute
2026-10-11 13:42 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-10 19:56 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-09 20:03 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-08 16:37 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-07 23:43 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-06 15:13 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-05 17:39 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-10-03 14:22 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-30 14:59 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-30 10:23 UTCEG score recompute
2026-09-28 13:46 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-28 13:17 UTCOSV refresh
2026-09-27 13:40 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-26 15:54 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-26 00:20 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-24 13:59 UTCEPSS rescoreEPSS 13% · 96th percentile
2026-09-22 14:43 UTCEPSS rescoreEPSS 13% · 96th percentile

Same product

10 shown

Debian:9:curl

Same vendor

10 shown

redhat:RHSA-2019:1543

Same CWE

10 shown

CWE-121 · CWE-787

Frequently asked(5)

What is CVE-2019-3822?

CVE-2019-3822 is a critical-severity vulnerability; its CVE record was published on February 6, 2019. 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…

When was CVE-2019-3822 made public?

CVE-2019-3822 was made public on February 6, 2019: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on February 6, 2019. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.

Is CVE-2019-3822 actively exploited?

CVE-2019-3822 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).

What is the CVSS score of CVE-2019-3822?

CVE-2019-3822 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2019-3822?

A fix for CVE-2019-3822 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-3822 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-3822

Explore →

Is Your Infrastructure Affected by CVE-2019-3822?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs

CVE-2019-3822

📅 Published

🔄 Last Modified

📋 Advisory Details (10)

myF5

NetApp Product Security

NetApp Product Security

cURL: Multiple vulnerabilities (GLSA 201903-03) — Gentoo security

Pony Mail

curl - NTLMv2 type-3 header stack buffer overflow - CVE-2019-3822

1670254 – (CVE-2019-3822) CVE-2019-3822 curl: NTLMv2 type-3 header stack buffer overflow

CVE-2019-3822 - PSIRT.COM

📣 Vendor Advisories for CVE-2019-3822(1)

Patch Availability(3)

Affected Packages

Weakness Classification(2)

Additional Vendor Advisories

Data Freshness Timeline

🔗 Related CVEs(same product + same vendor + same CWE)

Same product

Same vendor

Same CWE

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-3822?

Published

Last Modified

Advisory Details (10)

Vendor Advisories for CVE-2019-3822(1)

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)