Skip to content
Fencer Intel
medium 5.5

CVE-2019-2228 json

In array_find of array.c, there is a possible out-of-bounds read due to an incorrect bounds check.

published 6y ago modified 4mo ago also EUVD-2019-11870

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

In array_find of array.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure in the printer spooler with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-111210196

Patch / fix

  • cups Debian 14, Debian 13, Debian 12 2.3.1-1

debian advisories DEBIAN-CVE-2019-2228

  • cups Ubuntu 16.04 LTS 2.1.3-4ubuntu0.11
  • cups Ubuntu 18.04 LTS 2.2.7-1ubuntu2.8

ubuntu advisories UBUNTU-CVE-2019-2228

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • cups openSUSE Tumbleweed 2.3.3op2-4.2

opensuse advisories openSUSE-SU-2024:10707-1

Is CVE-2019-2228 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:C/I:N/A:N

Affected products

  • n/a Android

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.