CVE-2022-36937
First published: Wed May 10 2023(Updated: )
HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension. TLS1.0 has numerous published vulnerabilities and is deprecated. HHVM 4.153.4, 4.168.2, 4.169.2, 4.170.2, 4.171.1, 4.172.1, 4.173.0 replaces TLS1.0 with TLS1.3. Applications that call stream_socket_server or stream_socket_client functions with a URL starting with tls:// are affected.
Credit: cve-assign@fb.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Facebook HHVM | <4.153.4 | |
| Facebook HHVM | >=4.154.0<4.168.2 | |
| Facebook HHVM | >=4.169.0<4.169.2 | |
| Facebook HHVM | >=4.170.0<4.170.2 | |
| Facebook HHVM | =4.171.0 | |
| Facebook HHVM | =4.172.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-36937?
CVE-2022-36937 is a vulnerability in HHVM (HipHop Virtual Machine) versions 4.172.0 and all prior versions that use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension.
What is the severity of CVE-2022-36937?
The severity of CVE-2022-36937 is critical, with a CVSS base score of 9.8.
How does TLS 1.0 affect HHVM?
TLS 1.0 poses a security risk for HHVM as it has numerous published vulnerabilities and is deprecated.
Which versions of HHVM are affected by CVE-2022-36937?
HHVM versions 4.172.0 and all prior versions are affected by CVE-2022-36937.
How can I mitigate CVE-2022-36937?
To mitigate CVE-2022-36937, upgrade your HHVM installation to version 4.153.4 or higher, which replaces TLS 1.0 with TLS 1.3.
- collector/nvd-index
- vendor/facebook
- canonical/facebook hhvm
- version/facebook hhvm/4.154.0
- version/facebook hhvm/4.169.0
- version/facebook hhvm/4.170.0
- version/facebook hhvm/4.171.0
- version/facebook hhvm/4.172.0