Nginx NJS 0.7.5 src/njs_djb_hash.c njs_djb_hash memory corruption
|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.
A vulnerability, which was classified as critical, has been found in Nginx NJS 0.7.5 (Web Server). This issue affects the function
njs_djb_hash of the file src/njs_djb_hash.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The software 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. The impact remains unknown. The summary by CVE is:
Nginx NJS v0.7.5 was discovered to contain a segmentation violation via njs_djb_hash at src/njs_djb_hash.c.
The weakness was shared 07/19/2022 as 540. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-34030 since 06/20/2022. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/06/2022).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
CVSSv3VulDB 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: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Memory corruption
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔒
Timeline06/20/2022 CVE reserved
07/19/2022 +29 days Advisory disclosed
07/19/2022 +0 days VulDB entry created
08/06/2022 +18 days VulDB last update
CVE: CVE-2022-34030 (🔒)
EntryCreated: 07/19/2022 09:59 AM
Updated: 08/06/2022 10:53 AM
Changes: (11) vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss3_nvd_basescore vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!