Skip to content
Noroxi
CVE-2023-51430· NVD / CVE Program· CNA Honor

Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.

Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.

MediumCVSS 5.5 · v3.1—No exploit No fix recorded
Published
Dec 29, 2023
Updated
Jun 17, 2026
EPSS
0.2% · 4th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Honor
4.4
1.1 point gap

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
hihonormagic ui

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • hihonor magic uibefore 6.1.0.212

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Honor). Independent of NVD's CPE analysis and usually ahead of it.

  • Honor Magic UI

    • 6.0 and later · before 6.1.0.212affected

Other highest-scoring records for the same primary product.

  • CVE-2023-51434 Some Honor products are affected by buffer overflow vulnerability, successful exploitation could cause code execution.
    31Monitor
  • CVE-2023-51435 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.
    28Monitor
  • CVE-2023-6939 Some Honor products are affected by type confusion vulnerability, successful exploitation could cause denial of service.
    22Monitor
  • CVE-2023-51433 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.
    22Monitor
  • CVE-2023-51432 Some Honor products are affected by out of bounds read vulnerability, successful exploitation could cause information leak.
    22Monitor
  • CVE-2023-23441 Some Honor products are affected by out of bounds read vulnerability, successful exploitation could cause information leak.
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-514350 days apart Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.
    28Monitor
  • CVE-2023-514330 days apart Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak.
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records