CVE-2019-2201

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

Published: 2019-11-13 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-2201 is rated Moderate Risk (59.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.46%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-2201

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-04 2.73% 2.46% -0.27%
2 2026-06-15 1.47% 2.73% +1.27%
3 2026-05-30 — 1.47% —

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-2201

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2019-2201

OS Trackers for CVE-2019-2201

vendor priority summary link
alpine high CVE-2019-2201: 1 source package rows (libjpeg-turbo); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2019-2201
debian low CVE-2019-2201 low priority: Debian including 1 source packages (libjpeg-turbo), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-2201
gentoo normal CVE-2019-2201: 1 GLSA(s) (202003-23), 1 atom(s) (media-libs/libjpeg-turbo); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-2201
redhat medium — https://access.redhat.com/security/cve/CVE-2019-2201
suse high CVE-2019-2201 severity important: SUSE including 309 source package names (0.38.1:libjpeg8-8.1.2-5.12.1, 0.45.0.7.7.1:libjpeg8-8.1.2-5.12.1, …), 545 product×package rows across 92 product lines (Container bci/openjdk, Container bci/openjdk-devel, … (92 product lines)): Fixed 314, Known Affected 231. https://www.suse.com/security/cve/CVE-2019-2201/
ubuntu medium CVE-2019-2201 medium priority: Ubuntu including 1 source packages (libjpeg-turbo), 6 status rows across 6 suites (bionic, disco, eoan, trusty, upstream, xenial): released 3, not-affected 2, needs-triage 1. https://ubuntu.com/security/CVE-2019-2201

Affected software / configurations for CVE-2019-2201

Vendor Product Version Raw CPE
google android 8.0 cpe:2.3:o:google:android:8.0:*:*:*:*:*:*:*
google android 8.1 cpe:2.3:o:google:android:8.1:*:*:*:*:*:*:*
google android 9.0 cpe:2.3:o:google:android:9.0:*:*:*:*:*:*:*
google android 10.0 cpe:2.3:o:google:android:10.0:*:*:*:*:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 19.04 cpe:2.3:o:canonical:ubuntu_linux:19.04:*:*:*:*:*:*:*

References for CVE-2019-2201

cvelogic Threat Intelligence