Summaryinfo

A vulnerability classified as critical was found in Nginx NJS 0.7.5. This vulnerability affects the function njs_utf8_next of the file src/njs_utf8.h. The manipulation leads to memory corruption. This vulnerability was named CVE-2022-34028. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Detailsinfo

A vulnerability classified as critical has been found in Nginx NJS 0.7.5 (Web Server). This affects the function njs_utf8_next of the file src/njs_utf8.h. 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 summary by CVE is:

Nginx NJS v0.7.5 was discovered to contain a segmentation violation via njs_utf8_next at src/njs_utf8.h.

The weakness was disclosed 07/19/2022 as 522. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-34028 since 06/20/2022. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Web Server

Vendor

• Nginx

Name

• NJS

Version

• 0.7.5

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion