LiveActive security incident?Get immediate response
CVE Record

CVE-2022-39008: The NFC module has bundle serialization/deserialization vulnerabilities.

The NFC module has bundle serialization/deserialization vulnerabilities. Successful exploitation of this vulnerability may cause third-party apps to read and write files that are accessible only to system apps.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This Huawei NFC flaw could let third-party apps access files normally reserved for system apps. That creates serious confidentiality and integrity risk on affected mobile devices, especially where corporate data or privileged app data is present. The public bundle does not confirm exploitation in the wild.

Executive priority

Treat this as high-priority mobile fleet remediation where affected Huawei devices are present. The issue enables access to protected system-app files, which can affect sensitive data integrity and confidentiality, but current sources do not prove active exploitation.

Technical view

CVE-2022-39008 is a CWE-502 serialization/deserialization issue in Huawei's NFC module affecting HarmonyOS 2.0 and EMUI 12.0.0. Huawei describes possible read/write access to system-app-only files by third-party apps. CVSS 3.1 is 9.1 with network attack vector, no privileges, no user interaction, and high confidentiality/integrity impact.

Likely exposure

Exposure is limited to Huawei devices running HarmonyOS 2.0 or EMUI 12.0.0, per the source bundle. Organizations with managed Huawei mobile fleets, BYOD Huawei devices, or NFC-enabled workflows should inventory these OS versions and verify bulletin coverage.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates low-complexity, unauthenticated, no-user-interaction exploitation, but public source detail is insufficient to describe exact triggering conditions or attack paths.

Researcher notes

Public detail is sparse. Do not assume affected versions beyond HarmonyOS 2.0 and EMUI 12.0.0. Focus validation on version inventory, Huawei bulletin mapping, and patch status. Avoid claiming exploitability specifics beyond the CVSS vector and Huawei description.

Mitigation direction

  • Review Huawei's September 2022 security bulletin for affected models and update guidance.
  • Prioritize security updates for HarmonyOS 2.0 and EMUI 12.0.0 devices.
  • Use MDM controls to identify and isolate unpatched affected Huawei devices.
  • Limit untrusted third-party app installation on affected devices until remediated.
  • Follow Huawei guidance if a model lacks an available update.

Validation and detection

  • Inventory Huawei devices and record OS family, version, and security patch level.
  • Compare device versions against HarmonyOS 2.0 and EMUI 12.0.0 affected entries.
  • Confirm applicable Huawei September 2022 updates are installed where available.
  • Check MDM compliance reports for remaining affected or unsupported devices.
  • Document exceptions and compensating controls for devices that cannot be updated.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-39008 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2022-39008Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HuaweiHarmonyOS2.0Listed
HuaweiEMUI12.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.