Local sensitive-file access via incorrect default permissions
Published Nov 20, 2023 · Updated Aug 29, 2024
Incorrect default permissions in the LiteOS-A kernel of OpenHarmony 3.2.0 through 3.2.2 allow local users to read or rewrite sensitive files. OpenHarmony has not identified the affected file, permission mode, or code path that assigns the unsafe defaults. Local device access is required; the published impact is exposure of confidential information or modification of sensitive files.
Summary
What happened
Incorrect default permissions in the LiteOS-A kernel of OpenHarmony 3.2.0 through 3.2.2 allow local users to read or rewrite sensitive files. OpenHarmony has not identified the affected file, permission mode, or code path that assigns the unsafe defaults. Local device access is required; the published impact is exposure of confidential information or modification of sensitive files.
The record
- CVE
- CVE-2023-3116
- Published
- Nov 20, 2023
- Updated
- Aug 29, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-276, T1565.001, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 29, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v3.2.0 <=v3.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo