PJSIP PJSUA API pjsua_recorder_create filename out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in PJSIP. Affected by this vulnerability is the function pjsua_recorder_create of the component PJSUA API. Performing a manipulation of the argument filename results in out-of-bounds.
This vulnerability is identified as CVE-2021-43302. There is not any exploit available.
Details
A vulnerability was found in PJSIP (the affected version is unknown). It has been classified as problematic. This affects the function pjsua_recorder_create of the component PJSUA API. The manipulation of the argument filename with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality.
The weakness was released 02/17/2022 as GHSA-qcvw-h34v-c7r9. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-43302 since 11/03/2021. 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/03/2021 🔍02/17/2022 🔍
02/17/2022 🔍
11/05/2025 🔍
Sources
Advisory: GHSA-qcvw-h34v-c7r9Status: Confirmed
CVE: CVE-2021-43302 (🔍)
GCVE (CVE): GCVE-0-2021-43302
GCVE (VulDB): GCVE-100-193281
Entry
Created: 02/17/2022 08:27Updated: 11/05/2025 02:00
Changes: 02/17/2022 08:27 (38), 02/19/2022 12:09 (1), 02/19/2022 12:17 (1), 11/05/2025 02:00 (33)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.