CVE-2024-4767
Mozilla Firefox ≤ 115.11.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NSummary
CVE-2024-4767 is a medium-severity Incomplete Cleanup (CWE-459) vulnerability in Mozilla Firefox. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-21 (Information Sharing) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44362
Vulnerability Data
If the `browser.privatebrowsing.autostart` preference is enabled, IndexedDB files were not properly deleted when the window was closed. This preference is disabled by default in Firefox. This vulnerability affects Firefox < 126, Firefox ESR < 115.11, and Thunderbird < 115.11.
- 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
V10.3.5V10.7.2V6.4.1
Mitigating Controls (NIST 800-53 r5) AI
Enforces authorizations so that PII is not reachable by unauthorized actors.
Requires explicit verification that a recipient's authorizations match the sensitivity of shared PII.
Limits granted rights to the minimum needed, reducing the set of actors who can reach private data.
Documents the legal or consent basis required before any processing of PII occurs.
Implements consent mechanisms that directly block access absent the individual's permission.
Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.
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-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.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
CWE-359 does not impair RC.CO-04's ability to issue approved public recovery updates, yet any resulting PII exposure can partially undermine the outcome's overall efficacy and trust.
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 temporary or residual data, directly addressing incomplete cleanup.
Masking or anonymizing personal identifiers limits the amount of private personal information that can be disclosed through application outputs or logs.
Monitoring and quarantining outbound messages that contain personal or private data directly reduces the chance that such information will be disclosed to unauthorized recipients.
The explicit prohibition on copying personally identifiable information into development and test environments directly lowers the exposure of private personal data to staff or processes that should not see it.
Labeling, chain-of-custody, and access-control requirements limit the exposure of private personal information during any transfer method.
Mandating privacy procedures and a designated privacy officer helps ensure that private personal information is not disclosed without proper authorization or necessity.
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).
Ubuntu 22.04 (1 rule)
- V-260531 Ubuntu 22.04 LTS must configure the SSH daemon to use FIPS 140-3-approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. prevents CWE-359
Ubuntu 24.04 (1 rule)
- V-270670 Ubuntu 24.04 LTS must configure the SSH client to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. prevents CWE-359