EmuiOperating system · Huawei

CVE-2022-48302

HIGH · 7.5 CVSS v3.1 Published 2023-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The AMS module has a vulnerability of lacking permission verification in APIs.Successful exploitation of this vulnerability may affect data confidentiality.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a broken access control vulnerability in the AMS module where API endpoints lack proper permission verification. An attacker can potentially access unauthorized data or functionality by making API calls without proper authorization checks, leading to confidentiality breaches.

MitigationImplement robust permission verification and authorization checks at the API layer for all AMS module endpoints, following the principle of least privilege.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EmuiOperating system
Affected:= 11.0.1= 12.0.0= 12.0.1
HarmonyosOperating system
Affected:= 2.0= 2.1= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Huawei EMUI version
    Go to Settings > About Phone on the Huawei device and locate the EMUI version number
    Affected if The EMUI version is 11.0.1, 12.0.0, or 12.0.1
  2. Check Huawei HarmonyOS version
    Go to Settings > About Phone on the Huawei device and locate the HarmonyOS version number
    Affected if The HarmonyOS version is 2.0, 2.1, or 3.0.0
  3. Identify if AMS module API endpoints are exposed
    Review application or system configurations to determine if the AMS (Application Management System) module has accessible API endpoints
    Affected if AMS module API endpoints are accessible and the OS version matches affected versions
  4. Verify authorization mechanism on AMS APIs
    Test API calls to AMS module endpoints without providing authorization credentials or with insufficient permissions
    Affected if API calls succeed without proper authorization checks returning unauthorized data or functionality

A user is affected if their device runs Huawei EMUI 11.0.1, 12.0.0, or 12.0.1, or HarmonyOS 2.0, 2.1, or 3.0.0, and the AMS module API endpoints can be accessed without proper permission verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust permission verification and authorization checks at the API layer for all AMS module endpoints, following the principle of least privilege.

Fix this in Emui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-48302 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data