Unauthorized access vulnerability in the card management module.
Noroxi assessment
Priority: Monitor (action score 30/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.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
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
Primary sources: NVD · CVE.org · FIRST EPSS
Unauthorized access vulnerability in the card management module. Successful exploitation of this vulnerability may affect service confidentiality.
- Published
- Dec 6, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- CWE-863
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei emui11.0.1
- huawei emui12.0.0
- huawei emui13.0.0
- huawei harmonyos2.0.0
- huawei harmonyos3.0.0
- huawei harmonyos3.1.0
- huawei harmonyos4.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
Huawei EMUI
- 13.0.0, 12.0.0, 11.0.1affected
Huawei HarmonyOS
- 4.0.0, 3.1.0, 3.0.0, 2.0.0affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-57961Out-of-bounds write vulnerability in the emcom module
Impact: Successful exploitation of this vulnerability may cause features to perform ab39Monitor
- CVE-2024-57959Use-After-Free (UAF) vulnerability in the display module
Impact: Successful exploitation of this vulnerability may cause features to perform39Monitor
- CVE-2024-32991Permission verification vulnerability in the wpa_supplicant module
Impact: Successful exploitation of this vulnerability will affect availab39Monitor
- CVE-2023-52381Script injection vulnerability in the email module.Successful exploitation of this vulnerability may affect service confidentiality, integri39Monitor
- CVE-2023-52378Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this vulnerability may cause feature39Monitor
- CVE-2023-52370Stack overflow vulnerability in the network acceleration module.Successful exploitation of this vulnerability may cause unauthorized file ac39Monitor
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.
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-2021-46890154 days apartVulnerability of incomplete read and write permission verification in the GPU module.39Monitor
- CVE-2023-492460 days apartUnauthorized access vulnerability in the card management module.30Monitor
- CVE-2023-5237474 days apartPermission control vulnerability in the package management module.Successful exploitation of this vulnerability may affect service confident30Monitor
- CVE-2023-34161170 days apartnappropriate authorization vulnerability in the SettingsProvider module.Successful exploitation of this vulnerability may cause features to 30Monitor
- CVE-2023-31226194 days apartThe SDK for the MediaPlaybackController module has improper permission verification.30Monitor
- CVE-2024-9136296 days apartAccess permission verification vulnerability in the App Multiplier module
Impact: Successful exploitation of this vulnerability may affect s30Monitor
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.