dbcve.org
AndroidOperating system · Samsung

CVE-2023-21441

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-09
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
Insufficient Verification of Data Authenticity vulnerability in Routine prior to versions 2.6.30.6 in Android Q(10), 3.1.21.10 in Android R(11) and 3.5.2.23 in Android S(12) allows local attacker to access protected files via unused code.

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

Insufficient verification of data authenticity in Samsung's Routine application allows a local attacker to access protected files through unused code paths. This is a file access vulnerability in the Routine app affecting Android Q, R, and S versions prior to the patched releases.

MitigationUpdate the Routine application to version 2.6.30.6 (Android Q), 3.1.21.10 (Android R), or 3.5.2.23 (Android S) or later to remediate the vulnerability.

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. Verify the Routine application is installed
    Use the device's package manager to list installed packages and confirm com.samsung.android.routine (or similar Routine package name) is present on the device
    Affected if The Routine app is present on the device and its version cannot be verified or is below the fixed releases
  2. Determine the installed Routine app version
    Query the package manager for the version name and version code of the Routine application (e.g., via 'adb shell dumpsys package com.samsung.android.routine' or through device settings under Apps > Routine > App info)
    Affected if The version displayed is lower than 2.6.30.6 on Android Q, lower than 3.1.21.10 on Android R, or lower than 3.5.2.23 on Android S
  3. Identify the Android OS version running on the device
    Check the Android version in Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if The device runs Android 10 (Q), Android 11 (R), or Android 12 (S)
  4. Cross-reference version against affected ranges
    Compare your confirmed Routine app version against the fixed versions for your Android release: Android Q requires 2.6.30.6 or later, Android R requires 3.1.21.10 or later, Android S requires 3.5.2.23 or later
    Affected if The installed Routine version is below the required fixed version for your Android release, meaning the vulnerability is present

A user is affected if the Samsung Routine app is installed with a version lower than 2.6.30.6 on Android 10, lower than 3.1.21.10 on Android 11, or lower than 3.5.2.23 on Android 12.

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 the Routine application to version 2.6.30.6 (Android Q), 3.1.21.10 (Android R), or 3.5.2.23 (Android S) or later to remediate the vulnerability.

Recommended fix High confidence

Routine app: 2.6.30.6 (Android Q/10), 3.1.21.10 (Android R/11), or 3.5.2.23 (Android S/12)

  1. Check the current version of the Samsung Routine app or feature on the device
  2. Update the device's system or Routine app to version 2.6.30.6 for Android Q (10)
  3. Update the device's system or Routine app to version 3.1.21.10 for Android R (11)
  4. Update the device's system or Routine app to version 3.5.2.23 for Android S (12)
  5. Verify the update was successfully applied by checking the Routine app version

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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