CVE-2023-51426
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 · uneditedSome Honor products are affected by type confusion vulnerability, successful exploitation could cause information leak.
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 · low confidenceType confusion vulnerability in Honor products allows attackers to cause an information leak. The vulnerability is network-exploitable with low complexity and no authentication required, but impact is limited to information disclosure rather than full system compromise.
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< 7.0.0.129CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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.
-
Confirm Honor device modelCheck the device settings under 'Settings' > 'About Phone' > 'Device Name' to confirm it is an Honor or Hihonor deviceAffected if Device is not an Honor or Hihonor product - this CVE does not apply to other vendors
-
Check Magic OS versionNavigate to 'Settings' > 'About Phone' > 'Magic OS version' or 'Software version' to view the installed OS version numberAffected if Magic OS version is not displayed or cannot be determined - version must be explicitly identified for this check
-
Compare version against affected rangeCompare the displayed version number to 7.0.0.129. The affected range is any version less than 7.0.0.129 (for example: 7.0.0.128, 6.x.x.x, etc.)Affected if Installed version is 7.0.0.129 or higher - the device is not in the affected version range
-
Verify network exposure (optional context)Check if the device has open network services or is directly accessible from untrusted networks - this vulnerability is network-exploitableAffected if Device is directly exposed to untrusted networks without firewall protection
The device is affected if it is an Honor/Hihonor product running Magic OS version lower than 7.0.0.129, as this is the specific version range identified as vulnerable to the type confusion flaw enabling information disclosure.
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 · scoped7.0.0.129
Apply vendor-provided security updates from Honor for affected products. Until a patch is available, minimize network exposure of vulnerable devices and monitor for indicators of compromise.
Magic OS 7.0.0.129 or later
- Check current Magic OS version on the Honor device
- Upgrade Magic OS to version 7.0.0.129 or later via system settings or Honor's official update mechanism
- After upgrade, verify the version has been successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51426 — 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-2023-51426 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