CVE-2024-41655
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-41655 is a high-severity Executable Regular Expression Error (CWE-624) vulnerability. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2298
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover regex patterns that accept or enable executable user input.
Development standards and tools can require safe regex construction and forbid known exponential patterns.
Security engineering principles applied during design require avoiding unsafe constructs such as executable regex with untrusted input.
Denial-of-service protections limit resource exhaustion caused by expensive regex evaluation.
Validating inputs before they reach a regex engine structurally blocks user-controlled executable components or modifiers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent use of executable regex with untrusted input via reviews, static analysis, and safe-coding standards.
Vulnerability identification processes can discover ReDoS issues in existing code but do not stop their introduction.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect executable regex flaws before production deployment.
Secure development lifecycle includes input validation and regex review that can prevent executable regex patterns.
Application security requirements can mandate safe regex handling and input sanitization.
Secure architecture principles discourage embedding user-controlled executable regex components.
Secure coding standards directly address safe regex construction and ban user-supplied pattern modifiers.