Local service interruption via reused security-component identifiers
Published Jun 8, 2025 · Updated Jun 9, 2025
Improper input validation in OpenHarmony 5.0.1 through 5.0.3 allows local users to interrupt service through a reused security-component ID. SecCompManager::CreateScId wraps its counter and formerly returned the next identifier without checking componentMap_ for an existing security component. A low-privileged local user can trigger an identifier collision without user interaction, disrupting availability without reported data disclosure or modification.
Summary
What happened
Improper input validation in OpenHarmony 5.0.1 through 5.0.3 allows local users to interrupt service through a reused security-component ID. SecCompManager::CreateScId wraps its counter and formerly returned the next identifier without checking componentMap_ for an existing security component. A low-privileged local user can trigger an identifier collision without user interaction, disrupting availability without reported data disclosure or modification.
The record
- CVE
- CVE-2025-27242
- Published
- Jun 8, 2025
- Updated
- Jun 9, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record 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=v5.0.1 <=v5.0.3
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.
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