Nginx njs 0.7.2 /src/njs_vmcode.c njs_vmcode_array null pointer dereference

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.
4.1$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Nginx njs 0.7.2. The impacted element is the function njs_vmcode_array of the file /src/njs_vmcode.c. This manipulation causes null pointer dereference. The identification of this vulnerability is CVE-2022-28049. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability classified as problematic was found in Nginx njs 0.7.2 (Web Server). Affected by this vulnerability is the function njs_vmcode_array of the file /src/njs_vmcode.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability.

The weakness was shared 04/15/2022 as 473. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2022-28049 since 03/28/2022. Technical details of the vulnerability are known, but there is no available exploit.

Applying the patch f65981b0b8fcf02d69a40bc934803c25c9f607ab is able to eliminate this problem. The bugfix is ready for download at github.com.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: f65981b0b8fcf02d69a40bc934803c25c9f607ab

Timelineinfo

03/28/2022 🔍
04/15/2022 +18 days 🔍
04/15/2022 +0 days 🔍
04/21/2022 +6 days 🔍

Sourcesinfo

Product: github.com

Advisory: 473
Status: Confirmed

CVE: CVE-2022-28049 (🔍)
GCVE (CVE): GCVE-0-2022-28049
GCVE (VulDB): GCVE-100-197479

Entryinfo

Created: 04/15/2022 19:11
Updated: 04/21/2022 07:45
Changes: 04/15/2022 19:11 (43), 04/21/2022 07:45 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!