CVE-2023-3116
Openatom Openharmony ≤ 3.2.2
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-3116 is a high-severity Incorrect Default Permissions (CWE-276) vulnerability in Openatom Openharmony. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-43802
Vulnerability Data
in OpenHarmony v3.2.2 and prior versions allow a local attacker get confidential information or rewrite sensitive file through incorrect default permissions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 2 OS baselines
—
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Access control policy can specify and enforce secure default permissions for resources.
Guides setting of default permissions to the minimum required level.
Establishes requirements for appropriate default permissions on system resources as part of configuration management.
Baseline establishment and updates on install/upgrade ensure correct default permissions rather than insecure ones.
Requiring the most restrictive settings instead of defaults prevents incorrect default permissions on resources.
Requires documented processes that include setting and maintaining correct default permissions for configuration items.
Requires addressing secure default permissions in physical and environmental protection controls.
Tailoring explicitly overrides or scopes default permission assignments in the baseline to match the system's actual risk and operational needs.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Hardened baselines and configuration management explicitly require correct default file permissions.
Defining and enforcing least-privilege access permissions directly prevents overly permissive defaults at install time.
Lifecycle management can encompass permission settings, yet the control is too broad to specifically mitigate incorrect defaults.
Secure SDLC practices include establishing secure defaults, but address only the development-phase portion of the weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's combined programme (code review, static analysis, vulnerability scanning, penetration testing) reaches CWE-276 from both SOURCE (installer scripts setting chmod/icacls are visible in code) and RUNTIME (pen tests and config scans routinely flag world-writable files); the remainder is bounded and nameable — binary-only third-party installers where source reach does not apply, and permission issues inherited from external configuration rather than the installer itself.
A.8.3 mandates access restriction including read/write/execute permissions per identity (guidance items b–d), so applying it to a system whose files were installed world-writable requires tightening those permissions, which removes the weakness as it exists in the operational system; the remainder is the product's installation process itself, which A.8.3 does not govern and which can re-introduce the flaw on reinstall or upgrade.
Standard templates that restrict access to utility programs and host parameter settings prevent the assignment of overly permissive default permissions on critical resources.
A.5.37 mandates documented operating procedures that explicitly include 'secure installation and configuration of systems,' so a well-implemented procedure specifying correct file permissions during installation prevents many instances of CWE-276; however, the procedures are fallible human practice, and many observed instances arise from vendor installer defaults the organization's procedure does not reach, leaving a nameable remainder — the same practice-not-mechanism boundary that graded A.8.28 partial.
Training installers and developers on secure default permissions reduces instances where world-writable or otherwise incorrect permissions are set during installation, but the practice is fallible and the strongest control for this weakness is configuration management establishing secure installation baselines; training reaches a minority of instances.
A.8.30 carries its effect through the contractual requirements for secure design, coding and testing practices (referencing 8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-276 is such an ordinary weakness, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134, with the same ceiling and the same fallible-practice remainder.
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 our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Windows Server 2016 (2 rules)
- V-224833 Permissions for program file directories must conform to minimum requirements. blocks CWE-276
- V-224834 Permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276
Windows Server 2019 (2 rules)
- V-205735 Windows Server 2019 permissions for program file directories must conform to minimum requirements. blocks CWE-276
- V-205736 Windows Server 2019 permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276