CVE-2023-23435
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 signature management vulnerability, successful exploitation could cause the forged system file overwrite the correct system file
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 confidenceA signature management vulnerability in certain Honor products allows attackers to overwrite legitimate system files with forged ones. Successful exploitation bypasses or fails proper cryptographic signature validation during system file installation or update processes.
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.1.0.137CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 the device runs Honor MagicosCheck the device settings: go to Settings > About Phone > OS Version, or look for 'Magicos' or 'Honor' in the system information. On Honor devices, the OS is typically labeled as Magicos.Affected if The device is running Honor Magicos as its operating system.
-
Identify the installed Magicos versionNavigate to Settings > About Phone > Version, or enter *#*#2846579#*#* to access engineering menu (if available). Record the full version number displayed.Affected if A Magicos version number is found on the device.
-
Compare version against the vulnerable rangeCompare your recorded version number to 7.1.0.137. Check if the first three numeric segments (7.1.0) are lower, or if 7.1.0.137 matches exactly but your build is older.Affected if The installed Magicos version is below 7.1.0.137 (for example, 7.1.0.130, 7.0.9.121, etc.).
-
Check if system update or file installation features are in useReview recent activity in Settings > System > Update, or check if OTA updates or manual firmware installation from external sources have been performed recently.Affected if The device has system update or firmware installation capability enabled and accessible.
-
Verify if official patches have been appliedCheck Settings > About Phone > Security patch level, or look for recent system update entries in the update history log.Affected if The device shows no update to version 7.1.0.137 or later, or the security patch level predates the CVE disclosure.
The device is affected if it runs Honor Magicos with a version number lower than 7.1.0.137 and has system file installation or update features enabled.
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.1.0.137
Apply vendor-supplied patches for affected Honor products; until patches are available, restrict device access to trusted networks and avoid installing untrusted applications or firmware updates.
MagicOS/Magicos 7.1.0.137 or later
- Open the Settings app on your Honor device
- Navigate to System & Updates
- Select Software Update
- Check for updates and install any available updates
- Ensure the updated version is 7.1.0.137 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23435 — 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-23435 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