LiteSpeed QUIC up to 3.0.x lsquic_qenc_hdl.c MAX_TABLE_CAPACITY Privilege Escalation
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability, which was classified as problematic, was found in LiteSpeed QUIC up to 3.0.x. This affects an unknown functionality of the file liblsquic/lsquic_qenc_hdl.c. The manipulation of the argument
MAX_TABLE_CAPACITY with an unknown input leads to a unknown weakness. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
liblsquic/lsquic_qenc_hdl.c in LiteSpeed QUIC (aka LSQUIC) before 3.1.0 mishandles MAX_TABLE_CAPACITY.
The weakness was released 05/12/2022 as a74702c630e108125e71898398737baec8f02238. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-30592 since 05/11/2022. The attack can only be done within the local network. The successful exploitation needs a authentication. Technical details are known, but no exploit is available.
Upgrading to version 3.1.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch a74702c630e108125e71898398737baec8f02238 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: QUIC 3.1.0
Timeline05/11/2022 CVE reserved
05/12/2022 +1 days Advisory disclosed
05/12/2022 +0 days VulDB entry created
05/14/2022 +2 days VulDB last update
CVE: CVE-2022-30592 (🔒)
EntryCreated: 05/12/2022 12:31 PM
Updated: 05/14/2022 02:43 PM
Changes: (1) source_cve_nvd_summary
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!