sparklemotion nokogiri c29c920907366cb74af13b4dc2230e9c9e23b833 hashmap.c hashmap_set_with_hash heap-based overflow ⚔ [Disputed]

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in sparklemotion nokogiri c29c920907366cb74af13b4dc2230e9c9e23b833. This affects the function hashmap_set_with_hash of the file gumbo-parser/src/hashmap.c. The manipulation leads to heap-based overflow. This vulnerability is documented as CVE-2025-6490. The attack needs to be performed locally. Additionally, an exploit exists. The actual existence of this vulnerability is currently in question. It is suggested to install a patch to address this issue. The project maintainer explains that the affected code was merged into the main branch but the commit never appeared in an official release.

Detailsinfo

A vulnerability was found in sparklemotion nokogiri c29c920907366cb74af13b4dc2230e9c9e23b833 and classified as problematic. This issue affects the function hashmap_set_with_hash of the file gumbo-parser/src/hashmap.c. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is availability.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-6490. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known.

The exploit is available at github.com. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. The project maintainer explains that the affected code was merged into the main branch but the commit never appeared in an official release.

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

The vulnerability is also documented in the databases at EUVD (EUVD-2025-18911) and CERT Bund (WID-SEC-2026-1687). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • IBM License Metric Tool

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.1

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 3.3
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

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

Timelineinfo

06/21/2025 🔍
06/21/2025 +0 days 🔍
05/28/2026 +340 days 🔍

Sourcesinfo

Product: github.com

Advisory: github.com
Status: Confirmed
Confirmation: 🔍
Disputed: 🔍

CVE: CVE-2025-6490 (🔍)
GCVE (CVE): GCVE-0-2025-6490
GCVE (VulDB): GCVE-100-313601
EUVD: 🔍
CERT Bund: WID-SEC-2026-1687 - IBM License Metric Tool: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 06/21/2025 17:14
Updated: 05/28/2026 01:57
Changes: 06/21/2025 17:14 (55), 06/22/2025 22:55 (30), 06/23/2025 20:50 (1), 06/30/2025 21:13 (13), 06/30/2025 22:27 (1), 05/28/2026 01:57 (7)
Complete: 🔍
Submitter: JJLeo
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #601005: sparklemotion nokogiri nokogiri v1.18.7 (commit a024cff) Heap-based Buffer Overflow (by JJLeo)

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!