dbcve.org
CameraApplication · Samsung

CVE-2022-33712

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 12.0.0.98 / 12.0.01.64 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
Intent redirection vulnerability using implict intent in Camera prior to versions 12.0.01.64 ,12.0.3.23, 12.0.0.98, 12.0.6.11, 12.0.3.19 in Android S(12) allows attacker to get sensitive information.

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

Intent redirection vulnerability in the Camera app on Android 12 allows a malicious application to intercept sensitive information by registering for implicit intents that the Camera app uses to transmit data. The vulnerability exists because the Camera app uses implicit intents instead of explicit intents for inter-component communication, enabling a malicious app to intercept the intent and access sensitive data.

MitigationUpdate Camera app to version 12.0.01.64, 12.0.3.23, 12.0.0.98, 12.0.6.11, or 12.0.3.19 or later. For development teams, refactor the Camera app to use explicit intents and validate the receiving component before dispatching sensitive data.

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:< 12.0.0.98> 12.0.01.0, < 12.0.01.64> 12.0.3.0, < 12.0.3.19> 12.0.3.19, < 12.0.3.23> 12.0.6.0, < 12.0.6.11

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Samsung Camera app version
    Go to Settings > Apps > Camera (or Samsung Camera), then check the Version information under App info. Alternatively, use ADB: adb shell dumpsys package com.sec.android.app.camera | grep versionName
    Affected if The displayed version falls into any of these ranges: < 12.0.0.98; > 12.0.01.0 and < 12.0.01.64; > 12.0.3.0 and < 12.0.3.19; > 12.0.3.19 and < 12.0.3.23; > 12.0.6.0 and < 12.0.6.11
  2. Confirm Android 12 is in use
    Check the device Android version in Settings > About Phone > Android version. This vulnerability affects Android 12 specifically.
    Affected if The device is running Android 12 with a vulnerable Samsung Camera version installed
  3. Verify intent handling configuration
    This vulnerability is inherent to the app architecture and cannot be directly inspected. The issue is that the Camera app transmits sensitive data via implicit intents that can be intercepted by other apps registered for those intent filters.
    Affected if The Camera app uses implicit intent mechanisms for inter-component communication (this is the default behavior in vulnerable versions)

You are affected if your Samsung Camera app version is within any of the affected ranges listed and the device is running Android 12, as the app will use implicit intents to transmit sensitive data that a malicious app could intercept.

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 12.0.0.98 / 12.0.01.64 / 12.0.3.19 or later
Fixed in 12.0.0.9812.0.01.6412.0.3.19
Interim mitigation

Update Camera app to version 12.0.01.64, 12.0.3.23, 12.0.0.98, 12.0.6.11, or 12.0.3.19 or later. For development teams, refactor the Camera app to use explicit intents and validate the receiving component before dispatching sensitive data.

Recommended fix High confidence

Camera app version 12.0.0.98, 12.0.01.64, 12.0.3.19, 12.0.3.23, or 12.0.6.11 (whichever is available for your device model)

  1. Open the Samsung Galaxy Store or Google Play Store on your device
  2. Search for 'Samsung Camera' or locate the Camera app in your app list
  3. Check the current installed version in App Info
  4. If the installed version is less than 12.0.0.98, upgrade to version 12.0.0.98 or higher
  5. If the installed version is between 12.0.01.0 and 12.0.01.63, upgrade to version 12.0.01.64 or higher
  6. If the installed version is between 12.0.3.0 and 12.0.3.18, upgrade to version 12.0.3.19 or higher
  7. If the installed version is between 12.0.3.19 and 12.0.3.22, upgrade to version 12.0.3.23 or higher
  8. Alternatively, check for system updates via Settings > Software Update > Download and install

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-2022-33712 — 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-33712 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