CVE-2024-38275
Moodle ≤ 4.1.11
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2024-38275 is a high-severity Sensitive Information in Resource Not Removed Before Reuse (CWE-226) vulnerability in Moodle Moodle. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 37th 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 MP-6 (Media Sanitization) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2114
Vulnerability Data
The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
V14.2.8V14.3.1V6.4.1
Mitigating Controls (NIST 800-53 r5) AI
MP-6 requires sanitization of media before release for reuse, directly stopping sensitive data from remaining in resources made available to others.
Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.
SC-4 requires preventing unintended information transfer through shared system resources such as memory, which is achieved by clearing data before reuse.
Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.
Session termination forces explicit release of session-related temporary resources.
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.
Explicit example calls for removing confidential data (e.g., from process memory) after use, directly preventing reuse of uncleared resources.
Secure-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
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.
Explicitly requires secure deletion of information before resources are reused or disposed.
Mandates secure disposal or re-use of equipment, covering media sanitization but not in-memory reuse.
Security testing can detect failures to sanitize resources before reuse.
Secure SDLC includes requirements for clearing sensitive data during resource lifecycle transitions.
Secure coding practices can prevent leaving sensitive data in memory or files before reuse.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.
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).
Oracle Linux 8 (1 rule)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-226
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. prevents CWE-226
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. prevents CWE-226
RHEL 9 (1 rule)
- V-257797 RHEL 9 must restrict access to the kernel message buffer. prevents CWE-226