CVE-2023-1719
Bitrix24 22.0.300
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2023-1719 is a high-severity Improper Initialization (CWE-665) vulnerability in Bitrix24 Bitrix24. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 9% 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-1719 is a global variable extraction flaw in Bitrix24 version 22.0.300 that stems from improper initialization of variables in the file bitrix/modules/main/tools.php. The issue is tracked as CWE-665 and carries a CVSS 3.1 score of 7.5.
Unauthenticated remote attackers can supply crafted input to overwrite uninitialized variables, enabling them to enumerate attachments stored on the server and to inject arbitrary JavaScript that executes in a victim browser. When the victim holds administrator privileges, the same technique may also permit arbitrary PHP code execution on the server.
Public advisories describing the vulnerability have been published at https://starlabs.sg/advisories/23/23-1719/.
The associated EPSS score currently stands at 0.8613, matching its observed peak.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23942
Vulnerability Data
Global variable extraction in bitrix/modules/main/tools.php in Bitrix24 22.0.300 allows unauthenticated remote attackers to (1) enumerate attachments on the server and (2) execute arbitrary JavaScript code in the victim's browser, and possibly execute arbitrary PHP code on the server if the…
more
victim has administrator privilege, via overwriting uninitialised variables.
- CWE(s)
Related Threats
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.
Ensures shared resources are explicitly initialized or cleared on allocation, preventing exposure of prior contents to new users or processes.
Mandates that every instance begins in a known (presumably clean) state, eliminating reliance on residual or uninitialized state left by prior executions.
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 enforce proper resource initialization during coding and testing.
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 uninitialized variables but does not itself enforce initialization practices.
Configuration management can enforce secure defaults and initialization settings but is not the primary control for code-level initialization.
Secure development life cycle mandates initialization checks and secure defaults that directly prevent improper resource initialization.
Secure system architecture and engineering principles require explicit initialization of resources and secure state management.
Secure coding standards explicitly forbid uninitialized variables and mandate proper resource initialization before use.