Security Resilience

CVE-2023-23432

Hihonor Nth-An00 Firmware ≤ 7.0.0.157

Published
29 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
EPSS Score 0.0011 1th percentile
Risk Priority 51 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-23432 is a high-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Hihonor Nth-An00 Firmware. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Invalid Code Signature (T1036.001); ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Some Honor products are affected by signature management vulnerability, successful exploitation could cause the forged system file overwrite the correct system file.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
T1505.006 vSphere Installation Bundles Persistence
Adversaries may abuse vSphere Installation Bundles (VIBs) to establish persistent access to ESXi hypervisors.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23433Same product: Hihonor Nth-An00 Firmware
CVE-2023-23431Same product: Hihonor Nth-An00 Firmware
CVE-2023-23424Same product: Hihonor Nth-An00 Firmware
CVE-2026-119192Shared CWE-347
CVE-2024-7479Shared CWE-347
CVE-2026-9793Shared CWE-347
CVE-2026-19505Shared CWE-347
CVE-2024-42004Shared CWE-347
CVE-2026-9487Shared CWE-347
CVE-2025-47949Shared CWE-347

Affected Assets

hihonor
nth-an00 firmware
≤ 7.0.0.157

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-347

Requires verification of digital signatures using organization-approved certificates before installation, directly preventing improper verification of cryptographic signatures.

addresses: CWE-347

Component authenticity commonly depends on cryptographic signatures; the control enforces proper verification of those signatures.

addresses: CWE-347

PKI certificates under an approved policy require cryptographic signature verification on issuance and validation.

addresses: CWE-347

Requires cryptographic signatures on authoritative data and support for verifying the chain of trust.

addresses: CWE-347

Mandates verification of cryptographic signatures (e.g., DNSSEC RRSIG) on resolution responses, addressing missing or bypassed signature checks.

addresses: CWE-347

Integrity tools commonly rely on cryptographic signatures whose improper validation this weakness covers.

addresses: CWE-347

Authenticity validation commonly relies on cryptographic signature or certificate checks that this control enforces.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.DS-01 mostly match
blocks

Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.

PR.DS-02 mostly match
blocks

Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.

ID.RA-09 partial match
blocks

Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.

PR.PS-06 partial match
blocks

Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's source reach (code review, SAST) catches the common case — missing or obviously misconfigured signature verification calls — and runtime reach (penetration testing) catches cases where unsigned or malformed data is accepted; the remainder is verification logic that is present but subtly incorrect (e.g., a verify flag set wrong, a check that accepts a null signature), which requires careful review or targeted test cases to surface.

prevents

Training technical teams on cryptographic practices (which A.6.3's education-and-training half explicitly covers) reduces signature-verification omissions where the defect is a knowledge gap or a deliberate shortcut, but most CWE-347 instances are implementation errors — wrong API, missing verify call, incorrect verification logic — that training does not reach, mirroring the A.6.3 vs CWE-598 anchor.

prevents

A.8.24 mandates approved cryptographic solutions and usage practices, which can require signature verification in code the organization writes, but the actual prevention of the code defect (calling or correctly using a verification API) depends on implementation rigor and does not reach third-party components or code that misuses approved cryptographic libraries.

prevents

A.8.28 mandates secure coding practices (standards, peer review, threat modelling, prohibition of insecure design techniques, use of vetted cryptographic components) that reduce the likelihood of improper signature verification being written, but it is a practice-based control whose effect depends on developer rigour; the weakness still arises where developers misuse verification APIs, omit checks, or use libraries that don't verify by default, leaving a nameable remainder that A.8.29 (security testing) is better positioned to catch.

finds

A.8.30's contractual requirements for secure coding/testing (8.25-8.29) and acceptance testing lead to finding CWE-347 instances through the testing programme it mandates, but the clause itself is a process/contractual wrapper — the actual finding is performed by the controls it requires, not by A.8.30 directly.

finds

A.8.8's reach is DISCLOSURE-based (vendor advisories, vulnerability scanning of known issues), and CWE-347 does surface as CVEs (observed examples include CVE-2002-1796, CVE-2005-2181/2182, CVE-2002-1706), so the disclosed third-party share is found; the majority of CWE-347 instances live in first-party code where developers wrote signature verification incorrectly, which A.8.8's scanning and advisory programme does not reach.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-347
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
Oracle Linux 9 (2 rules)
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. blocks CWE-347
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. blocks CWE-347
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
RHEL 8 (1 rule)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-347
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. blocks CWE-347

References