Skip to content
Fencer Intel
critical 9.3

CVE-2014-0978 json

Stack-based buffer overflow in the yyerror function in lib/cgraph/scan.l in Graphviz 2.34.0 allows remote attackers to have unspecified imp…

published 12y ago modified 4mo ago also EUVD-2014-1008

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

Summary

Stack-based buffer overflow in the yyerror function in lib/cgraph/scan.l in Graphviz 2.34.0 allows remote attackers to have unspecified impact via a long line in a dot file.

Patch / fix

  • graphviz Debian 14, Debian 13, Debian 12 2.26.3-16

debian advisories DEBIAN-CVE-2014-0978

Is CVE-2014-0978 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

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-0978 updated cvss 4.3

graphviz: stack-based buffer overflow in yyerror()

  • Red Hat Enterprise Linux 6 graphviz, graphviz-gd, graphviz-lua, graphviz-php, graphviz-tcl, graphviz-java, +5 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 graphviz, graphviz-gd, graphviz-lua, graphviz-php, graphviz-tcl, graphviz-java, +6 more
    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

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

Exploits and checks

  • github.com https://github.com/ellson/graphviz/commit/7aaddf52cd98589fb0c3ab72a393f8411838438a referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

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.