Nginx NJS 0.7.2 src/njs_value.c njs_value_own_enumerate memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Nginx NJS 0.7.2. This vulnerability affects the function njs_value_own_enumerate of the file src/njs_value.c. The manipulation results in memory corruption.
This vulnerability was named CVE-2022-29779. There is no available exploit.
A patch should be applied to remediate this issue.
Details
A vulnerability was found in Nginx NJS 0.7.2 (Web Server). It has been classified as critical. Affected is the function njs_value_own_enumerate of the file src/njs_value.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 06/03/2022 as 485. The advisory is available at github.com. This vulnerability is traded as CVE-2022-29779 since 04/25/2022. Technical details are known, but there is no available exploit.
Applying the patch 2e00e95473861846aa8538be87db07699d9f676d is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Product: https://github.com/nginx/njs/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.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: Memory corruptionCWE: CWE-119
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 2e00e95473861846aa8538be87db07699d9f676d
Timeline
04/25/2022 🔍06/03/2022 🔍
06/03/2022 🔍
06/06/2022 🔍
Sources
Product: github.comAdvisory: 485
Status: Confirmed
CVE: CVE-2022-29779 (🔍)
GCVE (CVE): GCVE-0-2022-29779
GCVE (VulDB): GCVE-100-201138
Entry
Created: 06/03/2022 09:34Updated: 06/06/2022 08:09
Changes: 06/03/2022 09:34 (43), 06/06/2022 08:09 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.