Skip to content
Fencer Intel
medium 6.8

CVE-2014-8625 json

Multiple format string vulnerabilities in the parse_error_msg function in parsehelp.c in dpkg before 1.17.22 allow remote attackers to caus…

published 2015-01-20 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-8462

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

Multiple format string vulnerabilities in the parse_error_msg function in parsehelp.c in dpkg before 1.17.22 allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers in the (1) package or (2) architecture name.

Patch / fix

  • dpkg Debian 14, Debian 13, Debian 12 1.17.22

debian advisories DEBIAN-CVE-2014-8625

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-8625 updated cvss 3.6

dpkg: format string vulnerability

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

Exploits and checks

  • bugs.debian.org https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768485 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/oss-sec/2014/q4/539 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.launchpad.net https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1389135 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-134 Use of Externally-Controlled Format String

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.