dbcve.org
Nth An00 FirmwareOperating system · Hihonor

CVE-2023-23431

HIGH · 7.1 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to 7.0.0.157 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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 · unedited
Some 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 · moderate confidence

This is a signature management vulnerability in Honor mobile devices that allows attackers to bypass code signing verification, enabling maliciously crafted system files to overwrite legitimate system files. The flaw appears to be in how the system validates cryptographic signatures before allowing file writes to protected system partitions.

MitigationApply the vendor-supplied firmware update from Honor/Huawei. If no update is available, consider device replacement or implement compensating controls such as restricting app installation sources and monitoring for suspicious system modifications.

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
Nth An00 FirmwareOperating system
Affected:< 7.0.0.157

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the device is Hihonor Nth An00 by reviewing the device information in Settings > About Phone > Model Number
    Affected if Device model is Hihonor Nth An00
  2. Check firmware version
    Navigate to Settings > About Phone > Version and compare the build number to 7.0.0.157. Use *#*#2846579#*#* or similar service codes if additional diagnostic menus are accessible.
    Affected if Firmware version is below 7.0.0.157
  3. Inspect system partition integrity
    Use ADB or root access to compare cryptographic hashes of critical system binaries (such as those in /system/bin or /system/vendor) against known-good baseline values. Look for unsigned or unexpectedly modified system files.
    Affected if System files show unexpected modifications or missing signature validations
  4. Verify code signing enforcement
    Check if signature verification is properly enforced by attempting to identify whether the device allows unsigned or improperly signed system modifications. Review any available audit logs for signature validation failures.
    Affected if Code signing verification can be bypassed or is disabled on the device

A user is affected if they own a Hihonor Nth An00 device running firmware version below 7.0.0.157 with exploitable signature verification on system partitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.0.157 or later
Fixed in 7.0.0.157
Interim mitigation

Apply the vendor-supplied firmware update from Honor/Huawei. If no update is available, consider device replacement or implement compensating controls such as restricting app installation sources and monitoring for suspicious system modifications.

Recommended fix Moderate confidence

Firmware version 7.0.0.157 or later for Honor devices with model designation Nth/An00

  1. Identify the specific Honor device model (the reference 'Nth An00' may correspond to a model number like NTH-AN00)
  2. Visit the official Honor support website at www.hihonor.com
  3. Navigate to the firmware/software update section for your specific device model
  4. Download the firmware version 7.0.0.157 or later from Honor's official source
  5. Follow Honor's official firmware upgrade instructions for your device, typically involving placing the update package on the device storage and initiating the update through Settings > System > Software Update, or using the HiSuite/Hisuite PC application
  6. Ensure the device has sufficient battery charge (recommended at least 50%) before initiating the update
  7. After successful update, verify the firmware version in Settings > About Phone to confirm version 7.0.0.157 or higher is installed
Caveat No breaking changes information provided in the available CVE description; standard firmware upgrade precautions apply (backup data, ensure stable power)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nth An00 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23431 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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