Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-33041 is a medium-severity Use of Out-of-range Pointer Offset (CWE-823) vulnerability in Qualcomm Fastconnect 6900 Firmware. Its CVSS base score is 6.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 3th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
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-2024-33041 is a memory corruption vulnerability arising from missing input parameter validation for the number of fences in fence frame IOCTL calls. It affects Qualcomm components and is linked to CWE-823 (Access of Uninitialized Pointer) and CWE-787 (Out-of-bounds Write). The vulnerability received a CVSS v3.1 base score of 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and was published on 2025-01-06.
The attack requires local access with high privileges, low complexity, and no user interaction. An attacker meeting these conditions can achieve high impacts on confidentiality, integrity, and availability, potentially leading to arbitrary code execution or system compromise through memory corruption.
The Qualcomm January 2025 Security Bulletin provides details on affected products and mitigation, available at https://docs.qualcomm.com/product/publicresources/securitybulletin/january-2025-bulletin.html.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-30786
Vulnerability Data
Memory corruption when input parameter validation for number of fences is missing for fence frame IOCTL calls,
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including static analysis and fuzzing) directly finds unsafe pointer arithmetic before deployment.
Requiring documented development standards and tools can mandate safe pointer usage and compiler/runtime checks that stop the weakness from being introduced.
Security engineering principles can require bounds-checked pointer arithmetic or safe language constructs that structurally avoid out-of-range offsets.
Process isolation confines damage from invalid pointer offsets to a single address space, reducing overall impact.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection controls limit the blast radius of an out-of-range pointer dereference without preventing or detecting the coding error itself.
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 require bounds-checked pointer arithmetic and static analysis to prevent out-of-range offsets.
SAST/DAST tools used for vulnerability identification can surface this class of coding defect.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 out-of-range pointer offsets before release.
Secure SDLC mandates input validation and bounds checking that can prevent out-of-range pointer offsets.
Application security requirements include memory-safety rules that reduce pointer-offset errors.
Secure architecture principles promote safe pointer handling and memory layout controls.
Secure coding standards directly forbid unsafe pointer arithmetic and require bounds checks.
Change management can enforce review gates that catch unsafe memory operations before deployment.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-823