dbcve.org
CalendarApplication · Samsung

CVE-2022-39915

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-08
Fix available
A fix is available. Upgrade to 11.6.08.0 / 12.2.11.3000 or later.
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
Improper access control vulnerability in Calendar prior to versions 11.6.08.0 in Android Q(10), 12.2.11.3000 in Android R(11), 12.3.07.2000 in Android S(12), and 12.4.02.0 in Android T(13) allows attackers to access sensitive information via implicit intent.

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 access control vulnerability in a Calendar Android application allows attackers to access sensitive calendar information through implicit intent handling. The app exposes sensitive data via inter-component communication without proper access controls, enabling potentially malicious apps on the same device to intercept this information.

MitigationUpdate Calendar app to patched versions (11.6.08.0 for Android Q, 12.2.11.3000 for Android R, 12.3.07.2000 for Android S, 12.4.02.0 for Android T). Additionally, refactor vulnerable intent handlers to use explicit intents with proper permission checks.

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
CalendarApplication
Affected:< 11.6.08.0< 12.2.11.3000< 12.3.07.2000< 12.4.02.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. Locate Samsung Calendar app
    Open Settings > Apps on the Android device and search for 'Samsung Calendar', or use ADB command: `adb shell pm list packages | grep calendar`
    Affected if The app package 'com.samsung.android.calendar' is installed on the device
  2. Determine installed Calendar version
    In Settings > Apps > Samsung Calendar, view the App info screen to find the version name and version code under 'App version'. Alternatively, use ADB: `adb shell dumpsys package com.samsung.android.calendar | grep versionName`
    Affected if The version shown is below 11.6.08.0, below 12.2.11.3000, below 12.3.07.2000, or below 12.4.02.0 depending on the Android OS version in use
  3. Identify Android OS version
    Go to Settings > About Phone > Android version to determine which Android release the device is running (Q=Android 10, R=Android 11, S=Android 12, T=Android 13)
    Affected if The Android OS version determines which version threshold applies: Q uses 11.6.08.0, R uses 12.2.11.3000, S uses 12.3.07.2000, T uses 12.4.02.0 as the minimum patched versions

If Samsung Calendar is installed and its version is below the threshold corresponding to the device's Android OS version, the app is vulnerable to implicit intent interception by malicious local apps.

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.0 / 12.2.11.3000 / 12.3.07.2000 or later
Fixed in 11.6.08.012.2.11.300012.3.07.2000
Interim mitigation

Update Calendar app to patched versions (11.6.08.0 for Android Q, 12.2.11.3000 for Android R, 12.3.07.2000 for Android S, 12.4.02.0 for Android T). Additionally, refactor vulnerable intent handlers to use explicit intents with proper permission checks.

Recommended fix High confidence

Calendar app version 11.6.08.0 (Android Q), 12.2.11.3000 (Android R), 12.3.07.2000 (Android S), or 12.4.02.0 (Android T) depending on Android version

  1. Identify the Android version of the Samsung device (Q=10, R=11, S=12, T=13)
  2. Open the Samsung Calendar app or device settings
  3. Navigate to the app info for Calendar
  4. Check the current Calendar app version installed
  5. Update the Calendar app to the version corresponding to the Android version: Android Q(10) to 11.6.08.0 or later; Android R(11) to 12.2.11.3000 or later; Android S(12) to 12.3.07.2000 or later; Android T(13) to 12.4.02.0 or later
  6. Update through Samsung Galaxy Store or device software update

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

Fix this in Calendar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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