CVE-2023-52376
Huawei Harmonyos 2.0.0 … 4.0.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-52376 is a high-severity Improper Removal of Sensitive Information Before Storage or Transfer (CWE-212) vulnerability in Huawei Harmonyos. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 26th 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 SI-19 (De-identification) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57032
Vulnerability Data
Information management vulnerability in the Gallery module.Successful exploitation of this vulnerability may affect service confidentiality.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V14.2.8V14.3.3
Mitigating Controls (NIST 800-53 r5) AI
Requires sanitization of media before disposal, release, or reuse, directly stopping sensitive information from remaining in resources made available to unauthorized parties.
Mandates removal of specified PII elements from datasets before further use or sharing, addressing a subset of the improper-removal cases.
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.
Directly addresses removal of confidential data from process memory and similar in-use contexts before exposure.
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.
A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule on labelling/classification controls, it has no direct preventing effect on a weakness unless and until another control (access, DLP, etc.) is configured to act on the resulting label.
Information-transfer rules can require sanitization of sensitive content before sharing.
A.5.34 only requires a privacy policy, procedures, assigned roles (e.g. privacy officer) and unspecified technical/organizational measures; it does not itself stop the improper retention of sensitive data before storage/transfer, so the weakness remains exploitable without depending on other controls.
A.8.10 mandates configuring systems for automatic secure deletion (overwriting, crypto erase, approved tools/providers) of sensitive data no longer required per retention policy, which stops most improper-removal cases from leaving recoverable sensitive information available to unauthorized actors; the bounded remainder is deletion of in-transit/temporary buffers or non-configurable embedded device memory where the control's automation and method selection do not reach.
A.8.11's masking/pseudonymization/anonymization techniques (plus access design and obfuscation rules) stop most exposures of the sensitive data that CWE-212 would otherwise transfer or store in the clear; the bounded remainder is data that must stay unmasked for functional reasons or where masking is not applied to every indirect identifier.
DLP policies can block or sanitize sensitive data before it leaves the system.
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` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. blocks CWE-212
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. blocks CWE-212
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-212
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. blocks CWE-212
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. blocks CWE-212