dbcve.org
Aquos Sh M02 FirmwareOperating system · Sharp

CVE-2020-5571

HIGH · 7.5 CVSS v3.1 Published 2020-04-23
Fix available
A fix is available. Upgrade to after 03.00.04 or later.
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
SHARP AQUOS series (AQUOS SH-M02 build number 01.00.05 and earlier, AQUOS SH-RM02 build number 01.00.04 and earlier, AQUOS mini SH-M03 build number 01.00.04 and earlier, AQUOS Keitai SH-N01 build number 01.00.01 and earlier, AQUOS L2 (UQ mobile/J:COM) build number 01.00.05 and earlier, AQUOS sense lite SH-M05 build number 03.00.04 and earlier, AQUOS sense (UQ mobile) build number 03.00.03 and earlier, AQUOS compact SH-M06 build number 02.00.02 and earlier, AQUOS sense plus SH-M07 build number 02.00.02 and earlier, AQUOS sense2 SH-M08 build number 02.00.05 and earlier, and AQUOS sense2 (UQ mobile) build number 02.00.06 and earlier) allow an attacker to obtain the sensitive information of the device via malicious applications installed on the device.

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 vulnerability in SHARP AQUOS series smartphones allows malicious applications installed on the device to obtain sensitive information. The issue likely stems from improper permission controls or insecure data storage that permits untrusted applications to access protected system data, contacts, or other confidential content without proper authorization checks.

MitigationUsers should avoid installing applications from untrusted sources and await official firmware updates from SHARP. Organizations should inventory affected devices and implement mobile device management (MDM) policies to restrict application installation permissions until patches are available.

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
Aquos Sh M02 FirmwareOperating system
Affected:<= 01.00.05
Aquos Sh Rm02 FirmwareOperating system
Affected:<= 01.00.04
Aquos Mini Sh M03 FirmwareOperating system
Affected:<= 01.00.04<= 01.00.01
Aquos L2 FirmwareOperating system
Affected:<= 01.00.05
Aquos Sense Lite Sh M05 FirmwareOperating system
Affected:<= 03.00.04
Aquos Sense FirmwareOperating system
Affected:<= 03.00.03
Aquos Compact Sh M06 FirmwareOperating system
Affected:<= 02.00.02
Aquos Sense Plus Sh M07 FirmwareOperating system
Affected:<= 0.2.00.02

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 model
    Check the device Settings > About Phone > Model name or use the command 'getprop ro.product.model' via ADB shell
    Affected if The model is not one of: Aquos Sh M02, Aquos Sh Rm02, Aquos Mini Sh M03, Aquos L2, Aquos Sense Lite Sh M05, Aquos Sense, Aquos Compact Sh M06, or Aquos Sense Plus Sh M07
  2. Check the firmware version
    Navigate to Settings > About Phone > Software Info > Build number or use 'getprop ro.build.version.release' via ADB shell
    Affected if Unable to retrieve firmware version information from the device
  3. Compare version to affected ranges
    Note the firmware version and compare against the affected version list for your specific model
    Affected if The installed firmware version is at or below: 01.00.05 for Aquos Sh M02; 01.00.04 for Aquos Sh Rm02; 01.00.04 or 01.00.01 for Aquos Mini Sh M03; 01.00.05 for Aquos L2; 03.00.04 for Aquos Sense Lite Sh M05; 03.00.03 for Aquos Sense; 02.00.02 for Aquos Compact Sh M06; 0.2.00.02 for Aquos Sense Plus S
  4. Verify application installation permissions
    Check Settings > Apps > Menu > Special access > Install unknown apps to see which sources are allowed
    Affected if Installation from unknown sources is enabled, increasing the attack surface for this vulnerability

The device is affected if it is one of the listed Sharp Aquos models AND its firmware version falls within or below the specified thresholds for that model.

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
Upgrade available Upgrade to a release after 03.00.04
Interim mitigation

Users should avoid installing applications from untrusted sources and await official firmware updates from SHARP. Organizations should inventory affected devices and implement mobile device management (MDM) policies to restrict application installation permissions until patches are available.

Fix this in Aquos Sh M02 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5571 — 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-2020-5571 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