CVE-2025-27247
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedin OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn OpenHarmony v5.0.3 and prior, a local attacker can exploit the get permission API to cause an information leak. The vulnerability stems from insufficient access controls on the permission getter function, allowing unauthorized local users to access sensitive permission-related information they should not have visibility into.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenHarmony versionCheck system settings or run 'getprop ro.build.version.sdk' or 'cat /proc/version' to determine the installed OpenHarmony versionAffected if Version is 5.0.3 or prior (any version up to and including 5.0.3)
-
Locate permission getter APISearch for permission-related API binaries or services in the system (typically under /system/bin or /vendor/bin) - look for permission manager or access control daemonsAffected if The permission getter functionality exists and is exposed on the system
-
Verify API accessibilityTest whether the permission getter API can be invoked by a non-privileged local user account (different from system/admin users)Affected if Non-privileged users can query permission information through the API without authentication or authorization failures
-
Check for sensitive information exposureQuery the permission API using a standard user account and inspect the output for permission details that should be restricted (such as other apps permissions, system permissions, or protected permission grants)Affected if The API returns permission data that the querying user should not have visibility into based on least-privilege principles
If your OpenHarmony version is 5.0.3 or prior AND the permission getter API is accessible to unauthorized local users, you are affected by this information leak vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patch for OpenHarmony v5.0.3 when available. As a interim measure, restrict local access to permission-related system calls and audit permission configurations.
OpenHarmony 5.0.4 or later
- Identify all OpenHarmony devices/systems running version 5.0.3 or prior
- Consult the official OpenHarmony release notes or gitee.com repository for version 5.0.4 or later releases that address this vulnerability
- Obtain the official OpenHarmony update package from trusted sources
- Follow the standard OpenHarmony OTA or firmware update process to apply the upgrade
- Verify the system is running a version newer than 5.0.3 after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27247 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data