CVE-2023-1718
DoS in Bitrix24 22.0.300
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2023-1718 is a high-severity Infinite Loop (CWE-835) vulnerability in Bitrix24 Bitrix24. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-1718 is an improper file stream access vulnerability in the Bitrix24 22.0.300 component located at /desktop_app/file.ajax.php?action=uploadfile. The flaw, tracked under CWE-835, permits remote manipulation of the tmp_url parameter and produces a high-impact denial-of-service condition without requiring authentication or user interaction. The issue received a CVSS 3.1 base score of 7.5 reflecting network attack vector, low complexity, and availability impact only.
Unauthenticated attackers with network access can submit a crafted tmp_url value to the affected endpoint, triggering resource exhaustion that renders the application unavailable to legitimate users. No privileges or special conditions beyond a standard HTTP request are needed for successful exploitation.
Public references point to detailed technical analysis from Star Labs but do not describe vendor patches or configuration work-arounds in the supplied data. The associated EPSS score has remained flat at 0.5115 with no material increase after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23941
Vulnerability Data
Improper file stream access in /desktop_app/file.ajax.php?action=uploadfile in Bitrix24 22.0.300 allows unauthenticated remote attackers to cause denial-of-service via a crafted "tmp_url".
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
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.
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.
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 uncover infinite-loop conditions before release.
Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.
Application security requirements can specify loop-termination rules, indirectly reducing the weakness.
Secure coding standards directly address loop termination and prevent infinite loops.
Secure architecture principles encourage designs that avoid unreachable exit conditions.
Change management can require review of loop logic when code is modified.