dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2019-2201

HIGH · 7.8 CVSS v3.1 Published 2019-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 generate_jsimd_ycc_rgb_convert_neon of jsimd_arm64_neon.S, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution in an unprivileged process with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-120551338

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

The vulnerability exists in libjpeg-turbo's ARM64 NEON SIMD optimization code (jsimd_arm64_neon.S), specifically in the generate_jsimd_ycc_rgb_convert_neon function used for YCbCr to RGB color space conversion during JPEG image processing. A missing bounds check allows an out-of-bounds write, potentially enabling remote code execution in an unprivileged process that processes a specially crafted JPEG image.

MitigationApply the Android security patch for the relevant月度安全公告 (monthly security bulletin) containing the fix for A-120551338, which updates the libjpeg-turbo component with proper bounds checking in the NEON code path.

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
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.04
AndroidOperating system
Affected:= 8.0= 8.1= 9.0= 10.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Confirm libjpeg-turbo is installed
    Check for the presence of libjpeg-turbo libraries: dpkg -l | grep libjpeg-turbo on Ubuntu, or look for libjpeg-turbo.so or libturbojpeg.so in /usr/lib/ on Android
    Affected if libjpeg-turbo is present on the system
  2. Identify the installed version
    Run 'dpkg -s libjpeg-turbo' on Ubuntu or check the library file version with 'strings /usr/lib/aarch64-linux-gnu/libjpeg-turbo.so.62 | grep "^\d"' (adjust path as needed)
    Affected if The installed version matches Ubuntu 16.04 (1.5.x), 18.04 (1.7.x), or 19.04 (2.0.x) packages that contain the vulnerable NEON code
  3. Verify ARM64 architecture
    Check the system architecture with 'uname -m' or 'dpkg --print-architecture'. The vulnerability is in ARM64 NEON SIMD code.
    Affected if The system runs on aarch64 (ARM64) architecture
  4. Confirm NEON SIMD is enabled
    Check if the jsimd_arm64_neon.S code path is being used. This is typically enabled by default when compiling libjpeg-turbo with NEON support. Verify by checking if the binary links to libjpeg-turbo with NEON optimization capability.
    Affected if NEON SIMD optimizations are enabled in the libjpeg-turbo build (default for ARM64 builds)
  5. Check for JPEG processing exposure
    Identify applications or services that process untrusted JPEG images using libjpeg-turbo. Look for image processing services, web servers, or apps that handle user-uploaded content.
    Affected if Applications that process JPEG images using libjpeg-turbo are running on the ARM64 system

A system is affected if it runs libjpeg-turbo on ARM64 architecture with NEON SIMD enabled and processes JPEG images, particularly on Ubuntu 16.04, 18.04, 19.04 or Android 8.0-10.0 versions containing the vulnerable NEON code path.

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 Android security patch for the relevant月度安全公告 (monthly security bulletin) containing the fix for A-120551338, which updates the libjpeg-turbo component with proper bounds checking in the NEON code path.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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