CVE-2024-24914
Checkpoint Gaia Os r81 … r81.20
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-24914 is a high-severity Improper Control of Dynamically-Identified Variables (CWE-914) vulnerability in Checkpoint Gaia Os. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Manipulation (T1565); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-22277
Vulnerability Data
Authenticated Gaia users can inject code or commands by global variables through special HTTP requests. A Security fix that mitigates this vulnerability is available.
- 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 unauthorized reads/writes to any named resource, including dynamically identified variables.
Input validation on variable identifiers stops malformed or unauthorized dynamic names from being used.
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 dynamic variable control flaws via coding standards, reviews, 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 and prevent dynamic-variable weaknesses before release.
Secure development lifecycle requires input validation and variable handling rules that reduce dynamic-variable misuse.
Application security requirements can mandate strict control over dynamically-identified variables.
Secure architecture principles discourage unsafe dynamic variable access patterns.
Secure coding standards directly prohibit uncontrolled dynamic variable access.