dbcve.org
AndroidOperating system · Google

CVE-2022-28780

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Improper access control vulnerability in Weather prior to SMR May-2022 Release 1 allows that attackers can access location information that set in Weather without permission. The patch adds proper protection to prevent access to location information.

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 Samsung's Weather application where the app fails to properly enforce authorization checks before allowing access to user-configured location data. Attackers can potentially read location information without proper authentication or permission, exposing sensitive geolocation data.

MitigationApply the SMR May-2022 Release 1 patch which adds proper permission checks and authorization validation before allowing access to location information stored in the Weather application.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.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
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 checks

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

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Android version is 10.0, 11.0, or 12.0 (exact match)
  2. Verify Samsung Weather app is installed
    Check for 'com.sec.android.weather' package in Settings > Apps, or run 'pm list packages | grep weather' via ADB shell
    Affected if Samsung Weather application is present on the device
  3. Confirm location data exists in Weather app
    Open Samsung Weather app, add at least one location to enable location tracking features, or inspect app data via 'adb shell run-as com.sec.android.weather ls files/'
    Affected if Location data has been configured or stored in the Weather application
  4. Check for unauthorized location access
    Attempt to query Weather app content via intent or content provider without authentication, or review app logs for access attempts using 'logcat | grep -i weather'
    Affected if The app allows access to location data without proper authorization validation (vulnerable behavior present)
  5. Verify patch installation status
    Check Security Update level in Settings > About Phone > Software Information, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if Security patch level is earlier than May-2022 SMR (Samsung Monthly Release)

A device is affected if it runs Android 10.0, 11.0, or 12.0 with Samsung Weather app installed, has location data configured, and has a security patch level before the May-2022 SMR release.

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

Apply the SMR May-2022 Release 1 patch which adds proper permission checks and authorization validation before allowing access to location information stored in the Weather application.

Recommended fix Moderate confidence

SMR May-2022 Release 1 or later

  1. Check your current Android version in Settings > About Phone > Android version
  2. Go to Settings > Software update > Download and install
  3. Apply the SMR May-2022 Release 1 security patch or later
  4. After updating, verify the patch is installed by checking Settings > About Phone > Software information > Security patch level

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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