dbcve.org
AndroidOperating system · Google

CVE-2022-36853

HIGH · 7.5 CVSS v3.1 Published 2022-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 in Photo Editor prior to SMR Sep-2022 Release 1 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 · high confidence

This is an Android intent redirection vulnerability in Samsung's Photo Editor app. Intent redirection (or intent hijacking) occurs when an exported application component accepts arbitrary intents without proper validation, allowing a malicious app to trigger the vulnerable component and intercept sensitive data or access protected functionality. The vulnerability allows attackers to potentially obtain sensitive information from the device.

MitigationUsers should update their Samsung Photo Editor app to SMR Sep-2022 Release 1 or later. Organizations should verify that managed devices have received the security patch and consider applying mobile device management policies to restrict app activities if the update cannot be applied.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Samsung Photo Editor app is installed
    Check device app list for Samsung Photo Editor, or use ADB: pm list packages | grep -i photo
    Affected if The app is present on the device
  2. Check Android OS version
    Go to Settings > About Phone > Android version, or use ADB: getprop ro.build.version.release
    Affected if Android version is 10, 11, or 12
  3. Check Photo Editor app version
    Go to Settings > Apps > Photo Editor > App info > Version, or use ADB: dumpsys package com.samsung.android.app.cameraframework
    Affected if App version is earlier than SMR Sep-2022 Release 1

The environment is affected if Samsung Photo Editor is installed on Android 10, 11, or 12 with a version older than the SMR Sep-2022 Release 1 patch.

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

Users should update their Samsung Photo Editor app to SMR Sep-2022 Release 1 or later. Organizations should verify that managed devices have received the security patch and consider applying mobile device management policies to restrict app activities if the update cannot be applied.

Recommended fix Moderate confidence

SMR Sep-2022 Release 1 (Photo Editor)

  1. Open the Samsung Galaxy Store or Google Play Store on your Samsung Android device
  2. Search for "Photo Editor" or locate the Samsung Photo Editor app
  3. Update the Photo Editor app to the latest version (SMR Sep-2022 Release 1 or later)
  4. Verify the update was successful by checking the app version in Settings > Apps > Photo Editor > Version information
  5. Ensure your device is running Android 10, 11, or 12 as these are the affected versions

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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