CVE-2022-36846
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 · uneditedA heap-based overflow vulnerability in ConstructDictionary function 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 · moderate confidenceA heap-based buffer overflow in the ConstructDictionary function of Samsung's S Pen SDK library (libSDKRecognitionText.spensdk.samsung.so) on devices prior to SMR Sep-2022 Release 1 allows an attacker to overflow a heap buffer, causing memory corruption and potentially achieving arbitrary code execution.
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= 10.0= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the Android versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.sdk' via ADBAffected if The version is 10, 11, or 12 (these are the affected Android versions listed)
-
Verify the S Pen SDK library is presentLook for the library file 'libSDKRecognitionText.spensdk.samsung.so' on the device, typically in /system/lib or /vendor/lib directoriesAffected if The library file exists on the device - this confirms the vulnerable component is installed
-
Check the security patch levelGo to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' via ADBAffected if The security patch level is earlier than September 2022 (SMR Sep-2022 Release 1 is the patched version)
The device is affected if it runs Android 10, 11, or 12, has the S Pen SDK library installed, and has a security patch level before September 2022.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Samsung SMR Sep-2022 Release 1 or later security update to affected devices to patch the vulnerable ConstructDictionary function in the S Pen SDK library.
SMR Sep-2022 Release 1 (September 2022 Security Patch Level)
- Go to Settings on the Samsung device
- Navigate to System > System Update or Settings > About Phone > Software Update
- Check for available updates and download the September 2022 security update (SMR Sep-2022 Release 1) or later
- Install the update and restart the device
- Verify the security patch level is September 2022 or later by going to Settings > About Phone > Software Information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36846 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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