CVE-2024-36463
Zabbix 5.0.0 – 5.0.43
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-36463 is a medium-severity Access to Critical Private Variable via Public Method (CWE-767) vulnerability in Zabbix Zabbix. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); 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 AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-36340
Vulnerability Data
The implementation of atob in "Zabbix JS" allows to create a string with arbitrary content and use it to access internal properties of objects.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops public methods from reading or writing private variables by requiring explicit authorization checks on every access.
Least privilege limits which code paths may touch critical variables, reducing the chance that an overly broad public method can reach them.
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 public exposure of private variables via code review, static analysis, and encapsulation standards.
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 improper exposure of private variables during acceptance.
Secure development life cycle mandates encapsulation and access-control design practices.
Application security requirements can specify that private variables must remain inaccessible.
Secure architecture principles enforce encapsulation and least-privilege data access.
Secure coding standards explicitly forbid exposing private variables through public methods.
Information access restriction directly prevents public methods from exposing private variables.