CVE-2023-25156
Published: 15 February 2023
Summary
CVE-2023-25156 is a high-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Kiwitcms Kiwi Tcms. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 26.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0650
Vulnerability details
Kiwi TCMS, an open source test management system, does not impose rate limits in versions prior to 12.0. This makes it easier to attempt brute-force attacks against the login page. Users should upgrade to v12.0 or later to receive a…
more
patch. As a workaround, users may install and configure a rate-limiting proxy in front of Kiwi TCMS.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.
This control directly enforces limits on consecutive invalid logon attempts and automatic response (e.g., lockout) to prevent brute-force exploitation of authentication mechanisms.
Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.
Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.
Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.
Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.
Specific conditions can include excessive failed attempts, triggering stronger authentication that restricts brute-force exploitation.
Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.