CVE-2020-1793

Locked-app data disclosure via insufficient App Lock authentication

Published Mar 20, 2020 · Updated Aug 4, 2024

Improper authentication in affected Huawei Mate 20 and Mate 30 Pro firmware allows attackers to read data from locked applications. The App Lock component fails to perform sufficient authentication in certain physical-use scenarios before making protected application data available. Physical possession of the smartphone is required, and Huawei documents exposure of certain locked-application data without disclosing the precise triggering sequence.

CVSS severity3.5
Low
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in affected Huawei Mate 20 and Mate 30 Pro firmware allows attackers to read data from locked applications. The App Lock component fails to perform sufficient authentication in certain physical-use scenarios before making protected application data available. Physical possession of the smartphone is required, and Huawei documents exposure of certain locked-application data without disclosing the precise triggering sequence.

The record

CVE
CVE-2020-1793
Published
Mar 20, 2020
Updated
Aug 4, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-287, T1461
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 20, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

2.1NIST NVDAV:L/AC:L/Au:N/C:P/I:N/A:N
3.3HuaweiCVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C
4.6NIST NVDCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
3.5HuaweiCVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-287Improper Authentication
T1461Lockscreen Bypass

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo