Nginx NJS 0.7.10 src/njs_vmcode.c njs_vmcode_return memory corruption

HistoryDiffrelatejsonxmlCTI

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.
6.5	$0-$5k	0.00

Summaryinfo

A vulnerability marked as critical has been reported in Nginx NJS 0.7.10. Affected by this issue is the function njs_vmcode_return of the file src/njs_vmcode.c. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2023-27729. There is no exploit available.

Detailsinfo

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

Nginx NJS v0.7.10 was discovered to contain an illegal memcpy via the function njs_vmcode_return at src/njs_vmcode.c.

The weakness was shared 04/10/2023 as 619. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-27729 since 03/05/2023. 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-2023-31465). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Web Server

Vendor

Nginx

Name

Version

0.7.10

License

open-source

Website

Product: https://github.com/nginx/njs/

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Memory corruption
CWE: 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 Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/05/2023 🔍
04/10/2023 +35 days 🔍
04/10/2023 +0 days 🔍
11/21/2025 +956 days 🔍

Sourcesinfo

Product: github.com

Advisory: 619
Status: Confirmed

CVE: CVE-2023-27729 (🔍)
GCVE (CVE): GCVE-0-2023-27729
GCVE (VulDB): GCVE-100-225369
EUVD: 🔍

Entryinfo

Created: 04/10/2023 09:46
Updated: 11/21/2025 08:16
Changes: 04/10/2023 09:46 (41), 04/26/2023 13:28 (11), 11/21/2025 08:16 (16)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.