dbcve.org
AndroidOperating system · Google

CVE-2022-39852

HIGH · 7.8 CVSS v3.1 Published 2022-10-07
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 makeContactAGIF in libagifencoder.quram.so library prior to SMR Oct-2022 Release 1 allows attacker to perform code execution.

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 makeContactAGIF function of Samsung's libagifencoder.quram.so library allows arbitrary code execution via crafted GIF input. The vulnerability exists in the GIF encoding process for contact-related images and is exploitable without authentication.

MitigationApply Samsung's October 2022 Security Maintenance Release (SMR) or later, which contains the patched libagifencoder.quram.so library. Devices running older SMR versions remain vulnerable.

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. Locate the vulnerable library file
    Search for libagifencoder.quram.so on the device filesystem. Typical locations include /system/lib/, /vendor/lib/, or /system/vendor/lib/. Use command: find / -name 'libagifencoder.quram.so' 2>/dev/null
    Affected if The library file exists on the device, indicating the vulnerable component is present
  2. Identify the Android version
    Check the device Android version in Settings > About Phone > Android version. Alternatively, run: getprop ro.build.version.release
    Affected if The device runs Android 10, 11, or 12, which are the affected versions listed for this CVE
  3. Confirm the device vendor
    Check if the device is a Samsung device, as this library is proprietary to Samsung. Run: getprop ro.product.brand or getprop ro.manufacturer
    Affected if The device is a Samsung device running affected Android versions (the library is Samsung-specific)
  4. Check the Security Maintenance Release (SMR) version
    On Samsung devices, check the Samsung security patch level in Settings > About Phone > Software information > Build number, or run: getprop ro.build.version.sem
    Affected if The SMR version is older than October 2022, indicating the patch is not applied. Compare against the affected version ranges.

A device is affected if it is a Samsung device running Android 10, 11, or 12 with the libagifencoder.quram.so library present and an SMR version older than October 2022.

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 Samsung's October 2022 Security Maintenance Release (SMR) or later, which contains the patched libagifencoder.quram.so library. Devices running older SMR versions remain vulnerable.

Recommended fix High confidence

Samsung SMR Oct-2022 Release 1 (or later)

  1. Check the current Samsung Galaxy device model and Android version by going to Settings > About Phone
  2. Identify if the device is running Android 10, 11, or 12
  3. Check for a system software update by going to Settings > Software update > Download and install
  4. Apply the SMR Oct-2022 Release 1 or later security patch update from Samsung
  5. Verify the patch level has been updated to October 2022 or later via Settings > About Phone > Software information > Security patch level
Caveat Standard Samsung firmware update risks apply - ensure device is charged and backup is performed before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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