dbcve.org
ReminderApplication · Samsung

CVE-2022-23433

MEDIUM · 5.3 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 11.6.08.6000 / 12.2.05.6000 or later.
See remediation →
62/100
Remediation priority · Elevated
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 access control vulnerability in Reminder prior to versions 12.3.01.3000 in Android S(12), 12.2.05.6000 in Android R(11) and 11.6.08.6000 in Andoid Q(10) allows attackers to register reminders or execute exporeted activities remotely.

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 an improper access control vulnerability in the Reminder application for Android. The vulnerability allows unauthenticated remote attackers to register reminders or execute exported activities without proper authorization, likely due to missing or insufficient permission checks on exported components in the Android manifest.

MitigationUpdate the Reminder application to the patched versions (12.3.01.3000 for Android S, 12.2.05.6000 for Android R, or 11.6.08.6000 for Android Q) to remediate this improper access control issue.

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
ReminderApplication
Affected:< 12.3.01.3000< 12.2.05.6000< 11.6.08.6000

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Locate the Samsung Reminder application
    Open Android Settings > Apps > Find and tap on Samsung Reminder (or search for 'Reminder' if the app name varies)
    Affected if The application is not found in the app list, meaning the app is not installed
  2. Identify the installed version number
    In the Samsung Reminder app info screen, look for the 'Version' field (typically shown near the app name or under 'App info' > 'Version')
    Affected if The version number displayed is lower than any of the following: 12.3.01.3000, 12.2.05.6000, or 11.6.08.6000
  3. Confirm the Android OS version
    Go to Settings > About Phone > Android version (path may vary by device)
    Affected if The Android OS version determines which patch threshold applies (Q, R, or S) for version comparison purposes
  4. Compare against affected version ranges
    Cross-reference the installed Reminder version with the affected ranges: for Android S (Android 12) check if version < 12.3.01.3000; for Android R (Android 11) check if version < 12.2.05.6000; for Android Q (Android 10) check if version < 11.6.08.6000
    Affected if The installed version is lower than the corresponding threshold for your Android version, indicating the exported activity vulnerability is present

A user is affected if Samsung Reminder is installed and its version falls below 12.3.01.3000 (Android S), 12.2.05.6000 (Android R), or 11.6.08.6000 (Android Q), exposing exported components without proper authorization checks.

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
Upgrade available Upgrade to 11.6.08.6000 / 12.2.05.6000 / 12.3.01.3000 or later
Fixed in 11.6.08.600012.2.05.600012.3.01.3000
Interim mitigation

Update the Reminder application to the patched versions (12.3.01.3000 for Android S, 12.2.05.6000 for Android R, or 11.6.08.6000 for Android Q) to remediate this improper access control issue.

Recommended fix High confidence

Reminder app version 12.3.01.3000 (Android S), 12.2.05.6000 (Android R), or 11.6.08.6000 (Android Q)

  1. Check the current Reminder app version on the Samsung device
  2. Open Samsung Galaxy Store or navigate to device Settings > Apps > Reminder
  3. Update the Reminder app to version 12.3.01.3000 or higher for Android S(12) devices
  4. Update the Reminder app to version 12.2.05.6000 or higher for Android R(11) devices
  5. Update the Reminder app to version 11.6.08.6000 or higher for Android Q(10) devices
  6. Verify the update was applied successfully

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

Fix this in Reminder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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