dbcve.org
AndroidOperating system · Samsung

CVE-2023-30692

HIGH · 7.8 CVSS v3.1 Published 2023-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 input validation vulnerability in Evaluator prior to SMR Oct-2023 Release 1 allows local attackers to launch privileged 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 in the Evaluator component prior to the SMR Oct-2023 Release 1 allows local (unauthenticated or lower-privilege) attackers to bypass intended access controls and execute privileged activities. This is a classic privilege escalation vulnerability stemming from insufficient validation of user input before authorizing elevated operations.

MitigationApply the SMR Oct-2023 Release 1 patch or later to the Evaluator component. Additionally, audit all input validation points in the Evaluator to ensure proper sanitization and authorization checks are enforced before allowing privileged operations.

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:= 11.0= 12.0= 13.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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 manufacturer and model
    Check if the device is a Samsung device by reviewing the device info or system properties (e.g., 'getprop ro.product.brand' or check Settings > About Phone > Manufacturer)
    Affected if The device is not a Samsung device, this CVE does not apply as it affects only Samsung Android devices
  2. Determine the Android version
    Check the Android OS version in Settings > About Phone > Android version, or use 'getprop ro.build.version.release' via ADB
    Affected if The installed Android version is 11.0, 12.0, or 13.0 specifically; versions outside this range are not affected by this CVE
  3. Check if the Evaluator component is present
    Inspect installed packages for the Evaluator component using 'pm list packages' or check for the Evaluator APK/system component in the Samsung system image
    Affected if The Evaluator component exists on the device - this is the vulnerable component where input validation is lacking
  4. Verify the installed Samsung Android security patch level
    Check the Security patch level in Settings > About Phone > Software information, or use 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than the SMR Oct-2023 Release 1 patch - the vulnerability remains unpatched

A user is affected if they have a Samsung Android device running version 11.0, 12.0, or 13.0 with the Evaluator component present and a security patch level earlier than the October 2023 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 Oct-2023 Release 1 patch or later to the Evaluator component. Additionally, audit all input validation points in the Evaluator to ensure proper sanitization and authorization checks are enforced before allowing privileged operations.

Recommended fix High confidence

Samsung SMR (Security Monthly Release) October 2023 or later

  1. 1. Go to Settings on the Samsung Android device
  2. 2. Navigate to Settings > Software update
  3. 3. Tap on 'Download and install' to check for available updates
  4. 4. Apply the SMR Oct-2023 Release 1 or later security update
  5. 5. Verify the update was installed by checking Settings > About phone > Software information
Caveat Security updates typically have minimal risk of breaking changes; standard caution applies before updating

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 / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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