tcpreplay 4.4.1 tcprewrite common/get.c get_layer4_v6 assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in tcpreplay 4.4.1. It has been rated as critical. This impacts the function get_layer4_v6 of the file common/get.c of the component tcprewrite. This manipulation causes assertion.
This vulnerability appears as CVE-2022-27939. There is no available exploit.
Details
A vulnerability has been found in tcpreplay 4.4.1 and classified as problematic. Affected by this vulnerability is the function get_layer4_v6 of the file common/get.c of the component tcprewrite. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. As an impact it is known to affect availability.
The weakness was presented 03/26/2022 as 717. The advisory is shared at github.com. This vulnerability is known as CVE-2022-27939 since 03/26/2022. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-32427). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
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: AssertionCWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/26/2022 🔍03/26/2022 🔍
03/26/2022 🔍
05/15/2026 🔍
Sources
Advisory: 717Status: Confirmed
CVE: CVE-2022-27939 (🔍)
GCVE (CVE): GCVE-0-2022-27939
GCVE (VulDB): GCVE-100-195853
EUVD: 🔍
Entry
Created: 03/26/2022 15:24Updated: 05/15/2026 15:46
Changes: 03/26/2022 15:24 (39), 03/31/2022 07:12 (1), 05/15/2026 15:46 (15)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.