dbcve.org
AndroidOperating system · Google

CVE-2020-0495

MEDIUM · 5.5 CVSS v3.1 Published 2020-12-15
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
In decode_Huffman of JBig2_SddProc.cpp, there is a possible out of bounds write due to an integer overflow. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-155473137

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 confidence

In the decode_Huffman function of JBig2_SddProc.cpp, an integer overflow vulnerability exists that can lead to an out-of-bounds write. This occurs during JBIG2 document decoding, where insufficient bounds checking on Huffman decoding operations allows memory corruption. The resulting memory write beyond allocated buffers enables local information disclosure without requiring elevated privileges or user interaction.

MitigationApply the relevant Android security patch (A-155473137) for Android-11 from Google's monthly security bulletin. As this is a system-level library vulnerability in the JBIG2 decoder, the fix is delivered through platform-level updates rather than application-level changes.

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:= 11.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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 Android version is 11.0
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Alternatively, use 'adb shell dumpsys package --versions' to verify the platform version.
    Affected if The version is exactly 11.0 (Android 11) - this is the only affected version per the provided data.
  2. Identify JBIG2 decoder library presence
    Check for the presence of JBIG2-related system libraries in /system/lib or /vendor/lib (commonly libjbig2dec.so or libskia.so which contains JBIG2 decoding code). Use 'find /system -name "*jbig*"' or 'ls -la /system/lib/lib*' to list relevant libraries.
    Affected if The JBIG2 decoder library exists on the device, which is typical in Android system images containing PDF or document processing components.
  3. Verify if JBIG2 decoding is enabled in system services
    Check system services that may invoke JBIG2 decoding, typically related to PDF rendering or image processing. Use 'dumpsys' to list active services or check /proc/<pid>/maps for processes that have loaded JBIG2 libraries.
    Affected if Processes with PDF or document viewing capabilities are running and have loaded the vulnerable JBIG2 library code.
  4. Check for Skia library version
    Many Android devices use Skia (libskia.so) for image decoding which includes JBIG2 support. Run 'pm list packages -s' to identify preinstalled apps with document/image viewing, then check their usage of system graphics libraries.
    Affected if The device has applications that process JBIG2-encoded content and those apps use the system Skia or JBIG2 library present in Android 11.0.

A user is affected if they are running Android 11.0 and have any application that processes JBIG2-encoded documents or images, as the vulnerability resides in the system-level JBIG2 decoder library.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Android security patch (A-155473137) for Android-11 from Google's monthly security bulletin. As this is a system-level library vulnerability in the JBIG2 decoder, the fix is delivered through platform-level updates rather than application-level changes.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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