dbcve.org
AndroidOperating system · Google

CVE-2022-36862

HIGH · 7.8 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 →
80/100
Remediation priority · High
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
A heap-based overflow vulnerability in HWR::EngineCJK::Impl::Construct() in libSDKRecognitionText.spensdk.samsung.so library prior to SMR Sep-2022 Release 1 allows attacker to cause memory access fault.

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

Heap-based buffer overflow in the HWR::EngineCJK::Impl::Construct() function within Samsung's S-Pen SDK library (libSDKRecognitionText.spensdk.samsung.so) allows an attacker to corrupt heap memory and potentially achieve arbitrary code execution via specially crafted handwriting input data.

MitigationApply the Samsung SMR Sep-2022 Release 1 or later security update, which includes the patched version of libSDKRecognitionText.spensdk.samsung.so. Ensure all vulnerable Samsung devices running the affected S-Pen SDK are updated.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 10.0, 11.0, or 12.0 exactly
  2. Verify S-Pen SDK library presence
    Check for the existence of libSDKRecognitionText.spensdk.samsung.so in /system/lib/ or /vendor/lib/ directories, or search using 'find / -name libSDKRecognitionText.spensdk.samsung.so 2>/dev/null' via ADB
    Affected if The library file is present on the device
  3. Confirm S-Pen input is enabled
    Check if S-Pen or handwriting input features are active: go to Settings > S Pen > Air actions, or check if any S-Pen related input methods are enabled in Settings > Apps > Default apps > Input methods
    Affected if S-Pen or handwriting input functionality is enabled or available on the device
  4. Identify device manufacturer
    Check device manufacturer via Settings > About Phone > Manufacturer, or run 'getprop ro.product.manufacturer' via ADB
    Affected if Device is a Samsung model that supports S-Pen (Galaxy Note, Galaxy S series with S-Pen, etc.)

User is affected if running Android 10.0, 11.0, or 12.0 on a Samsung device with the libSDKRecognitionText.spensdk.samsung.so library present and S-Pen handwriting input features enabled.

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

Apply the Samsung SMR Sep-2022 Release 1 or later security update, which includes the patched version of libSDKRecognitionText.spensdk.samsung.so. Ensure all vulnerable Samsung devices running the affected S-Pen SDK are updated.

Recommended fix High confidence

Samsung Mobile Security (SMR) September 2022 Release 1 or later for Android 10, 11, and 12 devices

  1. Check your device's current Android Security Patch Level by going to Settings > About Phone > Software Information
  2. Verify if your device has received the Samsung Mobile Security (SMR) September 2022 Release 1 patch or later
  3. If not updated, go to Settings > Software Update and select 'Download and Install' to receive the latest Samsung security update
  4. Alternatively, contact your device manufacturer or carrier for the specific security update containing the fix for CVE-2022-36862
  5. After updating, confirm the Security Patch Level shows September 2022 or later
Caveat Security updates are cumulative; installing the September 2022 patch should not introduce breaking changes but will include all prior month's security fixes

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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