dbcve.org
AndroidOperating system · Google

CVE-2022-36848

MEDIUM · 5.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 →
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 Authorization vulnerability in setDualDARPolicyCmd prior to SMR Sep-2022 Release 1 allows local attackers to cause local permanent denial of service.

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

Improper authorization vulnerability in Samsung's setDualDARPolicyCmd component allows a local attacker to permanently deny service on affected mobile devices. The vulnerability exists in SMR versions prior to September 2022 Release 1, where authorization checks are insufficient before executing the dual data-at-rest policy command.

MitigationUpdate affected Samsung mobile devices to SMR September-2022 Release 1 or later to apply the authorization fix.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 device is a Samsung mobile phone
    Check the device model and manufacturer in Settings > About Phone > Model Number. Verify it is a Samsung Galaxy or other Samsung mobile device.
    Affected if Device is not a Samsung product - the vulnerability is in Samsung's implementation only.
  2. Check Android version
    Go to Settings > About Phone > Android version. Verify the installed Android version is 10.0, 11.0, or 12.0.
    Affected if Android version is 10.0, 11.0, or 12.0 - these are the affected versions per the CVE.
  3. Check Samsung Maintenance Release (SMR) version
    Go to Settings > About Phone > Software information > Service provider software version or Settings > About Phone > SMR (Samsung Maintenance Release) version. Look for a date code or version number.
    Affected if SMR version is prior to September 2022 Release 1 - this is the vulnerable version range. If the SMR shows September-2022 Release 1 or later, the device is not affected.
  4. Verify setDualDARPolicyCmd component availability
    This is a Samsung-specific system component related to Dual Data At Rest encryption policy. It can be checked via ADB using 'dumpsys package' to list system components or checking Samsung Knox/dual DAR configuration if accessible.
    Affected if The setDualDARPolicyCmd component exists and processes dual DAR policy commands without sufficient authorization checks on vulnerable SMR versions.

The device is affected if it is a Samsung mobile phone running Android 10.0, 11.0, or 12.0 with a Samsung Maintenance Release version prior to September 2022 Release 1.

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

Update affected Samsung mobile devices to SMR September-2022 Release 1 or later to apply the authorization fix.

Recommended fix Moderate confidence

SMR Sep-2022 Release 1 (or later security update)

  1. Go to Settings > About Phone > Software Update on your Samsung device
  2. Tap 'Check for updates' or 'Download updates manually'
  3. Download and install the SMR Sep-2022 Release 1 security update or later
  4. After installation, verify the Security Patch Level shows September 2022 or later in Settings > About Phone > Software Information > Security Patch Level

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

Fix this in Android 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 help mitigating

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-36848 — 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-36848 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