Skip to content
Fencer Vulns
high 8.8

CVE-2019-9656 json

An issue was discovered in LibOFX 0.9.14.

published 2019-03-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-19023

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

Summary

An issue was discovered in LibOFX 0.9.14. There is a NULL pointer dereference in the function OFXApplication::startElement in the file lib/ofx_sgml.cpp, as demonstrated by ofxdump.

Patch / fix

  • libofx Debian 14, Debian 13, Debian 12 1:0.9.15-1

debian advisories DEBIAN-CVE-2019-9656

  • libofx Ubuntu 16.04 LTS 1:0.9.10-1+deb8u2build0.16.04.1

ubuntu advisories UBUNTU-CVE-2019-9656

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

  • libofx SLE Workstation Extension 12 SP5, SLE Software Development Kit 12 SP5 0.9.9-3.10.1

suse advisories SUSE-SU-2024:3007-1

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-2019-9656 updated cvss 5.3

libofx: null pointer dereference in function OFXApplication::startElement in lib/ofx_sgml.cpp

  • 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

2.16% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/TeamSeri0us/pocs/tree/master/libofx referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Vulns 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.