CVE-2024-41655 json
TF2 Item Format Regular Expression Denial of Service vulnerability
published 2024-07-23 2 y ago modified 2026-09-10 1 mo ago also GHSA-8h55-q5qq-p685 , EUVD-2024-2298
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
TF2 Item Format helps users format TF2 items to the community standards. Versions of `tf2-item-format` since at least `4.2.6` and prior to `5.9.14` are vulnerable to a Regular Expression Denial of Service (ReDoS) attack when parsing crafted user input. This vulnerability can be exploited by an attacker to perform DoS attacks on any service that uses any `tf2-item-format` to parse user input. Version `5.9.14` contains a fix for the issue.
Patch / fix
- npm tf2-item-format 5.9.14
- danocmx node-tf2-item-format 5.9.14
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | tf2-item-format | >=4.2.6, <5.9.14 |
5.9.14 |
Affected products
- danocmx node-tf2-item-format
Classification
References
-
github.com
/danocmx/node-tf2-item-format/commit/5cffcc16a9261d6a937bda72bfe6830e02e31eec
web
-
github.com
/danocmx/node-tf2-item-format/security/advisories/GHSA-8h55-q5qq-p685
web
-
github.com
/danocmx/node-tf2-item-format/releases/tag/v5.9.14
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-41655
advisory
-
github.com
/danocmx/node-tf2-item-format
package
Sources
- CVE List CVE-2024-41655
- GitHub Advisory GHSA-8h55-q5qq-p685
- NVD CVE-2024-41655
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.