NVD / CVE Program· CNA huawei

CVE-2024-39673: Vulnerability of serialisation/deserialisation mismatch in the iAware module.

Noroxi assessment

Priority: Monitor (action score 28/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.12% (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.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

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

Vulnerability of serialisation/deserialisation mismatch in the iAware module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

HighCVSS 7.1 · v3.1—No exploit No fix recorded

Deserialization

Published: Jul 25, 2024
Updated: Jun 17, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-502

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.1
CNA · huawei: 6.8; 0.3 point gap

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

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

Is your version affected? Check it

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 help

Affected 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
huawei	emui	cpe:2.3:o:huawei:emui
huawei	harmonyos	cpe:2.3:o:huawei:harmonyos

Affected versions

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

huawei emui12.0.0
huawei emui13.0.0
huawei emui14.0.0
huawei harmonyos2.0.0
huawei harmonyos2.1.0
huawei harmonyos3.0.0
huawei harmonyos3.1.0
huawei harmonyos4.0.0
huawei harmonyos4.2.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
- 14.0.0, 13.0.0, 12.0.0affected
Huawei HarmonyOS
- 4.2.0, 4.0.0, 3.1.0, 3.0.0, 2.1.0, 2.0.0affected

Same product

huawei: all records

Other 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 ab
39Monitor
CVE-2024-57959Use-After-Free (UAF) vulnerability in the display module Impact: Successful exploitation of this vulnerability may cause features to perform
39Monitor
CVE-2024-32991Permission verification vulnerability in the wpa_supplicant module Impact: Successful exploitation of this vulnerability will affect availab
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-39671Jul 25, 2024 · Access control vulnerability in the security verification module.
22Monitor
← EarlierCVE-2024-39672Jul 25, 2024 · Memory request logic vulnerability in the memory module.
28Monitor
Later →CVE-2024-39674Jul 25, 2024 · Plaintext vulnerability in the Gallery search module.
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.

Credits

All researchers

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-26547486 days apartThe InputMethod module has a vulnerability of serialization/deserialization mismatch.
31Monitor
CVE-2023-52357159 days apartVulnerability of serialization/deserialization mismatch in the vibration framework.Successful exploitation of this vulnerability may affect
30Monitor
CVE-2025-31175256 days apartDeserialization mismatch vulnerability in the DSoftBus module Impact: Successful exploitation of this vulnerability may affect service integ
30Monitor
CVE-2023-26548486 days apartThe pgmng module has a vulnerability in serialization/deserialization.
30Monitor

Chain candidates

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

CVE-2024-4203814 days apartVulnerability of PIN enhancement failures in the screen lock module Impact: Successful exploitation of this vulnerability may affect service
31Monitor
CVE-2023-52540108 days apartVulnerability of improper authentication in the Iaware module.
30Monitor
CVE-2022-48621158 days apartVulnerability of missing authentication for critical functions in the Wi-Fi module.Successful exploitation of this vulnerability may affect
30Monitor
CVE-2023-52955166 days apartVulnerability of improper authentication in the ANS system service module Impact: Successful exploitation of this vulnerability may cause fe
30Monitor

Bug bounty scope

No known public program.

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1071 · Jul 26, 2024(Huawei Çoklu Ürün Güvenlik Bildirimi)

All national notices →

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: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

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

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

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

Vulnerable

python

1payload = sock.recv(65536)
2job = pickle.loads(payload)

Fixed

python

1payload = sock.recv(65536)
2if not hmac.compare_digest(sign(payload), header_sig):
3    raise PermissionError("invalid signature")
4job = JobSchema.validate(json.loads(payload))

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)

Object InjectionCAPEC-586likelihood: Medium · High

ATT&CK techniques

—

Change log

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

References

consumer.huawei.com/en/support/bulletin/2024/7/

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

All records