njs up to 0.3.1 nxt/nxt_utf8.h String.prototype.toBytes Negative Argument numeric error

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

Summaryinfo

A vulnerability was found in njs up to 0.3.1. It has been classified as problematic. Affected by this issue is the function String.prototype.toBytes of the file nxt/nxt_utf8.h. The manipulation as part of Negative Argument leads to numeric error. This vulnerability is documented as CVE-2019-11837. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in njs up to 0.3.1. It has been rated as problematic. This issue affects the function String.prototype.toBytes of the file nxt/nxt_utf8.h. The manipulation as part of a Negative Argument leads to a numeric error vulnerability. Using CWE to declare the problem leads to CWE-189. Impacted is availability. The summary by CVE is:

njs through 0.3.1, used in NGINX, has a segmentation fault in String.prototype.toBytes for negative arguments, related to nxt_utf8_next in nxt/nxt_utf8.h and njs_string_offset in njs/njs_string.c.

The bug was discovered 05/07/2019. The weakness was released 05/09/2019. The identification of this vulnerability is CVE-2019-11837 since 05/09/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.

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

Entries connected to this vulnerability are available at VDB-134533 and VDB-134532. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Nginx

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.4

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

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Numeric error
CWE: CWE-189
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/07/2019 🔍
05/09/2019 +2 days 🔍
05/09/2019 +0 days 🔍
05/10/2019 +1 days 🔍
09/15/2023 +1589 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2019-11837 (🔍)
GCVE (CVE): GCVE-0-2019-11837
GCVE (VulDB): GCVE-100-134531
See also: 🔍

Entryinfo

Created: 05/10/2019 06:39
Updated: 09/15/2023 10:35
Changes: 05/10/2019 06:39 (57), 06/08/2020 15:12 (1), 09/15/2023 10:35 (3)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!