swift-nio-http2 up to 1.19.1 HTTP/2 integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in swift-nio-http2 up to 1.19.1. It has been classified as problematic. This affects an unknown function of the component HTTP2 Handler. The manipulation leads to integer overflow. This vulnerability is uniquely identified as CVE-2022-24667. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, has been found in swift-nio-http2 up to 1.19.1. This issue affects an unknown code block of the component HTTP2 Handler. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is availability.
The weakness was disclosed 02/10/2022 as GHSA-w3f6-pc54-gfw7. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-24667 since 02/07/2022. The technical details are unknown and an exploit is not publicly available.
Upgrading eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
02/07/2022 🔍02/10/2022 🔍
02/10/2022 🔍
02/14/2022 🔍
Sources
Advisory: GHSA-w3f6-pc54-gfw7Status: Confirmed
CVE: CVE-2022-24667 (🔍)
GCVE (CVE): GCVE-0-2022-24667
GCVE (VulDB): GCVE-100-192827
Entry
Created: 02/10/2022 14:20Updated: 02/14/2022 13:54
Changes: 02/10/2022 14:20 (38), 02/14/2022 13:54 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.