dbcve.org
AndroidOperating system · Google

CVE-2022-30711

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 FeedsInfo 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 input validation vulnerability in the FeedsInfo component of Samsung mobile devices allows unauthenticated attackers to launch certain activities. The vulnerability exists in versions prior to the SMR (Samsung Maintenance Release) June 2022 Release 1 update.

MitigationUpdate affected Samsung devices to SMR June-2022 Release 1 or later to obtain the proper input validation fixes.

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 device is a Samsung mobile device
    Check the device manufacturer by running 'getprop ro.product.brand' or viewing the device info in Settings > About Phone
    Affected if Device manufacturer is not Samsung - this vulnerability only affects Samsung devices, not other Android devices
  2. Verify Android version is 10, 11, or 12
    Check Android version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release'
    Affected if Android version is not 10, 11, or 12 - only these versions are listed as affected in the CVE
  3. Check Samsung SMR (Maintenance Release) version
    Run 'getprop ro.build.version.sem' or check Samsung software version in Settings > Software update > Samsung software update. The June 2022 Release 1 corresponds to SMR version June 2022 or later
    Affected if SMR version is earlier than June 2022 Release 1 or cannot be determined - the vulnerability exists in versions prior to this update
  4. Verify FeedsInfo component is present
    Check for the FeedsInfo application component by examining installed packages using a package manager or checking 'pm list packages | grep feeds' via ADB if available
    Affected if FeedsInfo component is installed and active - this is the vulnerable component where improper input validation occurs

User is affected if they have a Samsung mobile device running Android 10, 11, or 12 with the FeedsInfo component and the Samsung SMR version is earlier than June 2022 Release 1

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

Update affected Samsung devices to SMR June-2022 Release 1 or later to obtain the proper input validation fixes.

Recommended fix High confidence

SMR Jun-2022 Release 1 (June 2022 Security Patch)

  1. Check current Android security patch level on the device by navigating to Settings > Security > Security update (or Settings > About phone > Software info > Security patch level on Samsung devices)
  2. Verify the security patch level shows June 2022 or later (SMR Jun-2022 Release 1)
  3. If the device shows an older security patch level, check for available system updates by going to Settings > Software update > Download and install
  4. Download and install any available security updates
  5. After installation, verify the security patch level reflects SMR Jun-2022 Release 1 or later

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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