CVE-2021-3720
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 · uneditedAn information disclosure vulnerability was reported in the Time Weather system widget on Legion Phone Pro (L79031) and Legion Phone2 Pro (L70081) that could allow other applications to access device GPS data.
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 confidenceAn information disclosure vulnerability in the Time Weather system widget on Legion Phone Pro (L79031) and Legion Phone2 Pro (L70081) allows other applications to access device GPS data without proper authorization, exposing user location information.
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< 12.5.231< 12.5.632CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device modelGo to Settings > About Phone > Model Number, or run `getprop ro.product.model` via ADB shell, to confirm if the device is Lenovo Legion Phone Pro (l79031) or Legion Phone2 Pro (l70081)Affected if The device model is not l79031 or l70081 (this CVE only affects these two specific models)
-
Check installed firmware versionGo to Settings > About Phone > Build Number, or run `getprop ro.build.version.release` via ADB shell, then compare against 12.5.231 for l79031 or 12.5.632 for l70081Affected if Firmware version is below 12.5.231 on Legion Phone Pro, or below 12.5.632 on Legion Phone2 Pro
-
Verify Time Weather widget presenceCheck the device home screen widgets or app drawer for a Weather widget application; on Lenovo Legion devices this is typically a pre-installed system widget named 'Time Weather' or 'Weather'Affected if The Time Weather widget is present on the device (the vulnerability exists within this specific widget)
-
Review location permissions granted to appsGo to Settings > Apps > Permissions > Location, or run `dumpsys package` via ADB to list apps with location permission; check if any untrusted third-party applications have location accessAffected if Any third-party (non-system) applications have been granted location permissions, as the flaw allows unauthorized apps to access GPS through the Weather widget
Your device is affected if it is a Lenovo Legion Phone Pro (l79031) with firmware below 12.5.231, or a Legion Phone2 Pro (l70081) with firmware below 12.5.632, and the Time Weather widget is present with other apps having location permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.5.23112.5.632
Apply vendor firmware/security update to address improper GPS data access controls in the Weather widget; until then, revoke location permissions from untrusted third-party applications.
Legion Phone Pro (L79031) firmware 12.5.231 or later; Legion Phone2 Pro (L70081) firmware 12.5.632 or later
- Check for system updates on your Legion Phone Pro (L79031) or Legion Phone2 Pro (L70081) device
- Ensure the device is connected to Wi-Fi and has sufficient battery (recommended to be charging)
- Navigate to Settings > System > System Update (or Settings > About Phone > System Update)
- Download and install the firmware update to version 12.5.231 or later for Legion Phone Pro (L79031), or version 12.5.632 or later for Legion Phone2 Pro (L70081)
- Restart the device if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3720 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-3720 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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