Cyber Resilience

CVE-2024-54157

Jetbrains Youtrack ≤ 2024.3.52635

Published
04 December 2024
Modified
30 January 2025
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0057 44th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-54157 is a medium-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Jetbrains Youtrack. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

In JetBrains YouTrack before 2024.3.52635 potential ReDoS was possible due to vulnerable RegExp in Ruby syntax detector

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-50574Same product: Jetbrains Youtrack
CVE-2024-54156Same product: Jetbrains Youtrack
CVE-2025-64684Same product: Jetbrains Youtrack
CVE-2024-28230Same product: Jetbrains Youtrack
CVE-2025-24458Same product: Jetbrains Youtrack
CVE-2026-49370Same product: Jetbrains Youtrack
CVE-2026-28193Same product: Jetbrains Youtrack
CVE-2026-57922Same product: Jetbrains Youtrack
CVE-2025-64773Same product: Jetbrains Youtrack
CVE-2026-57923Same product: Jetbrains Youtrack

Affected Assets

jetbrains
youtrack
≤ 2024.3.52635

Mitigating Controls

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent inefficient regex via reviews, static analysis, and safe libraries.

ID.RA-01 partial match
prevents

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.

detects

Security testing can detect and reject regex patterns with exponential worst-case complexity.

prevents

Secure development lifecycle mandates review of algorithmic efficiency, directly addressing ReDoS-prone regex.

prevents

Application security requirements can specify input-validation rules that limit regex complexity.

prevents

Secure architecture principles encourage avoidance of computationally expensive constructs such as catastrophic backtracking.

prevents

Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.

References