dbcve.org
CameraApplication · Samsung

CVE-2023-30730

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 11.0.16.43 / 12.0.07.53 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
Implicit intent hijacking vulnerability in Camera prior to versions 11.0.16.43 in Android 11, 12.1.00.30, 12.0.07.53, 12.1.03.10 in Android 12, and 13.0.01.43, 13.1.00.83 in Android 13 allows local attacker to access specific file.

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 · high confidence

This is an implicit intent hijacking vulnerability in Samsung's Camera app for Android. The app uses implicit intents (which don't specify a target component) instead of explicit intents, allowing a malicious local app to register a receiver for these intents and intercept data. Specifically, this allows a local attacker to access certain files that should be protected.

MitigationUpdate the Samsung Camera app to versions 11.0.16.43 (Android 11), 12.1.00.30/12.0.07.53/12.1.03.10 (Android 12), or 13.0.01.43/13.1.00.83 (Android 13) or later, which convert implicit intents to explicit intents to prevent hijacking.

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
CameraApplication
Affected:>= 11.0.00.00, < 11.0.16.43>= 12.0.00.00, < 12.0.07.53>= 12.1.00.00, < 12.1.00.30>= 12.1.03.00, < 12.1.03.10< 13.0.01.43>= 13.1.00.00, < 13.1.00.83

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. Identify if Samsung Camera is installed
    Check for the Samsung Camera app package using 'adb shell pm list packages | grep -i camera' or manually check in Settings > Apps. The package name is typically 'com.sec.android.app.camera'.
    Affected if The package 'com.sec.android.app.camera' is found on the device.
  2. Retrieve the installed Samsung Camera version
    Run 'adb shell dumpsys package com.sec.android.app.camera' and look for 'versionName' in the output, or view the version in the Google Play Store listing if available.
    Affected if The version name returned is one of the vulnerable versions.
  3. Compare the installed version against affected ranges
    Check if the version falls into any of these vulnerable ranges: 11.0.00.00 to 11.0.16.42, 12.0.00.00 to 12.0.07.52, 12.1.00.00 to 12.1.00.29, 12.1.03.00 to 12.1.03.09, any version below 13.0.01.43 (except already listed), or 13.1.00.00 to 13.1.00.82.
    Affected if The installed version matches any of the vulnerable ranges listed.
  4. Confirm device is Samsung
    Verify the device manufacturer by running 'adb shell getprop ro.product.manufacturer' or checking the device model in Settings > About Phone.
    Affected if The device is manufactured by Samsung, as this vulnerability is specific to Samsung's Camera implementation.

If Samsung Camera is installed on a Samsung device and its version falls below the fixed versions (11.0.16.43, 12.0.07.53, 12.1.00.30, 12.1.03.10, 13.0.01.43, or 13.1.00.83), the device is vulnerable to implicit intent hijacking.

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.0.16.43 / 12.0.07.53 / 12.1.00.30 or later
Fixed in 11.0.16.4312.0.07.5312.1.00.30
Interim mitigation

Update the Samsung Camera app to versions 11.0.16.43 (Android 11), 12.1.00.30/12.0.07.53/12.1.03.10 (Android 12), or 13.0.01.43/13.1.00.83 (Android 13) or later, which convert implicit intents to explicit intents to prevent hijacking.

Recommended fix High confidence

Camera app version 11.0.16.43 for Android 11; 12.0.07.53, 12.1.00.30, or 12.1.03.10 for Android 12; 13.0.01.43 or 13.1.00.83 for Android 13

  1. Identify the Android version of the device (Android 11, 12, or 13)
  2. Check the current Samsung Camera app version in Settings > Apps > Camera
  3. Update the Samsung Camera app through the Galaxy Store or Google Play Store to the fixed version corresponding to the Android version
  4. Alternatively, install the latest Android system update which includes the patched Camera app
  5. Verify the Camera app has been updated to version 11.0.16.43 (Android 11), 12.0.07.53 or 12.1.00.30 or 12.1.03.10 (Android 12), or 13.0.01.43 or 13.1.00.83 (Android 13)
Caveat Updating Samsung Camera app may introduce UI changes or require updated Galaxy Store/Play Store services; ensure device has sufficient battery before updating

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

Fix this in Camera Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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