Skip to content
Fencer Intel
medium 5.5

CVE-2019-1010069 json

moinejf abcm2ps 8.13.20 is affected by: Incorrect Access Control.

published 7y ago modified 4mo ago also EUVD-2019-1818

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

Summary

moinejf abcm2ps 8.13.20 is affected by: Incorrect Access Control. The impact is: Allows attackers to cause a denial of service attack via a crafted file. The component is: front.c, function txt_add. The fixed version is: after commit commit 08aef597656d065e86075f3d53fda89765845eae.

Patch / fix

  • abcm2ps Debian 14, Debian 13, Debian 12 8.14.2-0.1

debian advisories DEBIAN-CVE-2019-1010069

  • abcm2ps Ubuntu 18.04 LTS 7.8.9-1+deb9u1build0.18.04.1
  • abcm2ps Ubuntu Pro 16.04 LTS 7.8.9-1ubuntu0.16.04.1~esm1

ubuntu advisories UBUNTU-CVE-2019-1010069

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

Is CVE-2019-1010069 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.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • drive.google.com https://drive.google.com/drive/u/2/folders/1Y2IbtEr9v4l4Ruie_AY9BFJOHOGiDt7S referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/leesavide/abcm2ps/issues/18 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • moinejf abcm2ps

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.