What is the severity of CVE-2019-11940?

CVE-2019-11940 is considered a high severity vulnerability due to its potential to cause use-after-free conditions and undefined behavior.

How do I fix CVE-2019-11940?

To fix CVE-2019-11940, upgrade Proxygen to a version later than 2017.04.03.00.

What versions of Proxygen are affected by CVE-2019-11940?

CVE-2019-11940 affects Proxygen versions between 0.29.0 and 2017.04.03.00.

What vulnerability does CVE-2019-11940 exploit during the HTTP2 protocol?

CVE-2019-11940 exploits vulnerabilities in the HPACK header compression process, leading to potential header table corruption.

Is CVE-2019-11940 related to memory safety issues?

Yes, CVE-2019-11940 involves a use-after-free condition, indicating potential memory safety issues in the affected software.

Vulnerability/
CVE-2019-11940

critical

9.8

CWE

416

4/12/2019

4/8/2024

CVE-2019-11940: Use After Free

First published: Wed Dec 04 2019(Updated: )

In the course of decompressing HPACK inside the HTTP2 protocol, an unexpected sequence of header table resize operations can place the header table into a corrupted state, leading to a use-after-free condition and undefined behavior. This issue affects Proxygen from v0.29.0 until v2017.04.03.00.

Credit: cve-assign@fb.com

Affected Software	Affected Version	How to fix
Facebook Proxygen	>=0.29.0<=2017.04.03.00

Remedy

https://github.com/facebook/proxygen/commit/f43b134cc5c19d8532e7fb670a1c02e85f7a8d4f

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-11940?
CVE-2019-11940 is considered a high severity vulnerability due to its potential to cause use-after-free conditions and undefined behavior.
How do I fix CVE-2019-11940?
To fix CVE-2019-11940, upgrade Proxygen to a version later than 2017.04.03.00.
What versions of Proxygen are affected by CVE-2019-11940?
CVE-2019-11940 affects Proxygen versions between 0.29.0 and 2017.04.03.00.
What vulnerability does CVE-2019-11940 exploit during the HTTP2 protocol?
CVE-2019-11940 exploits vulnerabilities in the HPACK header compression process, leading to potential header table corruption.
Is CVE-2019-11940 related to memory safety issues?
Yes, CVE-2019-11940 involves a use-after-free condition, indicating potential memory safety issues in the affected software.

agent/references
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/weakness
agent/severity
agent/author
agent/remedy
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/tags
agent/event
agent/source
vendor/facebook
canonical/facebook proxygen
version/facebook proxygen/0.29.0
version/facebook proxygen/2017.04.03.00

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2019-11940?
CVE-2019-11940 is considered a high severity vulnerability due to its potential to cause use-after-free conditions and undefined behavior.
How do I fix CVE-2019-11940?
To fix CVE-2019-11940, upgrade Proxygen to a version later than 2017.04.03.00.
What versions of Proxygen are affected by CVE-2019-11940?
CVE-2019-11940 affects Proxygen versions between 0.29.0 and 2017.04.03.00.
What vulnerability does CVE-2019-11940 exploit during the HTTP2 protocol?
CVE-2019-11940 exploits vulnerabilities in the HPACK header compression process, leading to potential header table corruption.
Is CVE-2019-11940 related to memory safety issues?
Yes, CVE-2019-11940 involves a use-after-free condition, indicating potential memory safety issues in the affected software.