CVE-2022-38081: Tokensync in security subsystem has a permission bypass vulnerability. LAN attackers can bypass the distributed permission control.To take advantage of this weakness, attackers need another vulnerability to obtain system.
First published: Tue Sep 06 2022(Updated: )
OpenHarmony-v3.1.2 and prior versions have a permission bypass vulnerability. LAN attackers can bypass the distributed permission control.To take advantage of this weakness, attackers need another vulnerability to obtain system.
Credit: scy@openharmony.io
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Openharmony Openharmony | >=3.1<=3.1.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-38081?
CVE-2022-38081 is a permission bypass vulnerability in OpenHarmony-v3.1.2 and prior versions.
What is the severity of CVE-2022-38081?
CVE-2022-38081 has a severity rating of 5.5 (medium).
How does CVE-2022-38081 work?
CVE-2022-38081 allows LAN attackers to bypass the distributed permission control in OpenHarmony-v3.1.2 and prior versions.
How can an attacker exploit CVE-2022-38081?
To exploit CVE-2022-38081, an attacker would need another vulnerability to obtain system access.
Is there a fix for CVE-2022-38081?
It is recommended to update to a version of OpenHarmony that is not affected by this vulnerability.
- collector/nvd-index
- agent/weakness
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/last-modified-date
- agent/title
- agent/severity
- agent/description
- agent/event
- agent/tags
- agent/first-publish-date
- vendor/openharmony
- canonical/openharmony openharmony
- version/openharmony openharmony/3.1
- version/openharmony openharmony/3.1.2