dbcve.org
AndroidOperating system · Google

CVE-2022-30713

CRITICAL · 9.1 CVSS v3.1 Published 2022-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper validation vulnerability in LSOItemData prior to SMR Jun-2022 Release 1 allows attackers to launch certain activities.

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

Improper validation in LSOItemData component in Samsung Mobile (SMR) versions prior to June 2022 Release 1 allows attackers to launch certain activities. The vulnerability stems from insufficient input validation, potentially enabling unauthorized actions within the Samsung mobile software stack.

MitigationApply the SMR Jun-2022 Release 1 or later patch which addresses the improper validation in LSOItemData. Validate all data inputs and enforce proper bounds checking in affected 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
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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm Samsung firmware is in use
    Check if the device is running Samsung's custom Android firmware (SMR). On the device, go to Settings > About Phone > Software information and look for the 'Build number' or 'SMR' version field. Alternatively, run: `getprop ro.build.version.sem` or `getprop ro.build.PDA` to retrieve Samsung-specific build properties.
    Affected if The device is not running Samsung's SMR firmware (e.g., running stock Android on a non-Samsung device or a custom ROM).
  2. Check SMR version
    Retrieve the SMR (Samsung Maintenance Release) version. Run: `getprop ro.build.version.sem` or look in Settings > About Phone > Software information for the SMR release number. The affected versions are those prior to 'SMR Jun-2022 Release 1'.
    Affected if The SMR version is before the June 2022 Release 1 patch level (e.g., SMR May-2022, SMR Apr-2022, etc.).
  3. Verify Android version
    Check the Android OS version on the device. Go to Settings > About Phone > Android version, or run: `getprop ro.build.version.release`. The affected Android versions are 10.0, 11.0, and 12.0.
    Affected if The Android version is 10.0, 11.0, or 12.0.
  4. Confirm LSOItemData component presence
    LSOItemData is a Samsung internal component. Check for its presence by examining installed Samsung packages: `pm list packages | grep -i lso` or look for Samsung-related packages containing 'lso' in the name. The component is typically part of Samsung's framework.
    Affected if The device has Samsung's LSOItemData component installed (which is standard on Samsung devices running SMR firmware).

The device is affected if it is a Samsung device running SMR firmware prior to the June 2022 Release 1 patch, with Android version 10.0, 11.0, or 12.0, and has the LSOItemData component present.

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 Jun-2022 Release 1 or later patch which addresses the improper validation in LSOItemData. Validate all data inputs and enforce proper bounds checking in affected components.

Recommended fix Moderate confidence

SMR Jun-2022 Release 1 or later

  1. Check the current SMR (Samsung Maintenance Release) version on the Samsung device by going to Settings > About Phone > Software Information > Security patch level
  2. Navigate to Settings > Software Update and download/install the latest security update
  3. Verify the device is running SMR Jun-2022 Release 1 or later by checking the Security patch level in Settings > About Phone > Software Information
  4. If the update is not available through OTA, contact the device carrier or Samsung support for manual update availability
Caveat Security updates typically have minimal risk; verify device backup before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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