Permission bypass in distributed TokenSync controls
Published Sep 9, 2022 · Updated Sep 16, 2024
Permission bypass in OpenHarmony 3.1.2 and earlier allows attackers on the LAN to bypass distributed permission controls. OpenHarmony has not disclosed the exact TokenSync operation that mishandles permission checks. Exploitation requires an additional vulnerability to obtain system access; the record identifies integrity impact but no specific modified resource.
Summary
What happened
Permission bypass in OpenHarmony 3.1.2 and earlier allows attackers on the LAN to bypass distributed permission controls. OpenHarmony has not disclosed the exact TokenSync operation that mishandles permission checks. Exploitation requires an additional vulnerability to obtain system access; the record identifies integrity impact but no specific modified resource.
The record
- CVE
- CVE-2022-38081
- Published
- Sep 9, 2022
- Updated
- Sep 16, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-287, CWE-305
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=OpenHarmony-v3.1.x-Release <=3.1.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