dbcve.org
EmuiOperating system · Huawei

CVE-2023-41308

HIGH · 7.5 CVSS v3.1 Published 2023-09-27
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
Screenshot vulnerability in the input module. Successful exploitation of this vulnerability may affect 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

A vulnerability in the input module allows unauthorized screenshot capture, potentially exposing sensitive visual information on the affected system. The CVSS 7.5 score indicates high exploitability with significant confidentiality impact, though the specific attack vector and affected software remain unspecified in available documentation.

MitigationUntil vendor-specific patch guidance is available, restrict access to the input module interface, monitor for unusual screenshot or screen-capture activity, and apply defense-in-depth controls around any input handling components.

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:= 12.0= 12.0.1= 13.0.0
HarmonyosOperating system
Affected:= 2.0.0= 2.0.1= 2.1.0= 3.0.0= 3.1.0= 4.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. Identify the device Huawei EMUI or HarmonyOS version
    On the Huawei device, go to Settings > About Phone > Version to view the installed EMUI or HarmonyOS build number
    Affected if The installed version matches exactly: EMUI 12.0, 12.0.1, or 13.0.0; or HarmonyOS 2.0.0, 2.0.1, 2.1.0, 3.0.0, 3.1.0, or 4.0.0
  2. Confirm input module component is present
    Check if the device has an input module or input handling service active by reviewing installed system components or services in Settings > Apps > System Apps or via ADB with 'dumpsys' commands
    Affected if The input module component exists on the device and is enabled (this is required for the vulnerability to be exploitable)
  3. Audit screen capture permissions and recent activity
    Review Settings > Privacy > Permission Manager > Camera and Photos and Media for any apps with screen capture or overlay permissions; check for any unknown or unauthorized screen recording apps
    Affected if Any third-party or unknown app has been granted screen capture, display over other apps, or screenshot permissions without explicit user consent

The device is affected if it runs exactly one of the listed Huawei EMUI or HarmonyOS versions and the input module is active, allowing potential unauthorized screenshot access.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until vendor-specific patch guidance is available, restrict access to the input module interface, monitor for unusual screenshot or screen-capture activity, and apply defense-in-depth controls around any input handling components.

Recommended fix Moderate confidence

EMUI 13.0.1+ or HarmonyOS 3.0.1+ (latest available security release)

  1. 1. Identify the current EMUI or HarmonyOS version on the affected device by navigating to Settings > About Phone
  2. 2. Check if the device model is eligible for security updates by visiting consumer.huawei.com or device.harmonyos.com
  3. 3. Navigate to Settings > System & Updates > Software Update to check for available updates
  4. 4. If an update is available, ensure the device is connected to Wi-Fi and has at least 50% battery charge
  5. 5. Download and install the latest available security update for EMUI or HarmonyOS
  6. 6. After updating, verify the vulnerability is resolved by confirming the input module no longer logs sensitive information
Caveat Security updates typically do not introduce breaking changes but may reset some user preferences; ensure backup of settings before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2023-41308 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