Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service excepti
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- 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.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 3.3, NVD 5.5.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.
- Published
- Dec 26, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 4th percentile
- CWE
- CWE-203
Report tools
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
- 3.3
- 2.2 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| honor | magicos | cpe:2.3:o:honor:magicos |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- honor magicos8.0 and later · before 8.0.0.64
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 OS
- 8.0 and later · before 8.0.0.64affected
Same product
honor: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-47151Some Honor products are affected by file writing vulnerability, successful exploitation could cause code execution31Monitor
- CVE-2023-23429
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service except30Monitor
- CVE-2023-23428
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service except30Monitor
- CVE-2023-23427
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service except30Monitor
- CVE-2023-23442
Some Honor products are affected by type confusion vulnerability, successful exploitation could cause information leak.28Monitor
- CVE-2023-23436
Some Honor products are affected by signature management vulnerability, successful exploitation could cause the forged system file overwrit28Monitor
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.
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-471500 days apartSome Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.22Monitor
- CVE-2024-471530 days apartSome Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.22Monitor
- CVE-2024-471540 days apartSome Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.22Monitor
- CVE-2024-471550 days apartSome Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.22Monitor
- CVE-2024-471560 days apartInformation Leak Vulnerability in Honor Product22Monitor
- CVE-2024-89930 days apartSome Honor products are affected by information leak vulnerability, successful exploitation could cause the 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.