CVE-2019-11934 json
Improper handling of close_notify alerts can result in an out-of-bounds read in AsyncSSLSocket.
published 2019-12-04 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3591
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Improper handling of close_notify alerts can result in an out-of-bounds read in AsyncSSLSocket. This issue affects folly prior to v2019.11.04.00.
Patch / fix
Exploit prediction
1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Facebook folly
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/facebook/folly/commit/c321eb588909646c15aefde035fd3133ba32cdee
patch, third-party-advisory
-
facebook.com
/security/advisories/cve-2019-11934
third-party-advisory
Sources
- CVE List CVE-2019-11934
- NVD CVE-2019-11934
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.