Skip to content
Fencer Vulns
high 7.5

CVE-2017-2808 json

An exploitable use-after-free vulnerability exists in the account parsing component of the Ledger-CLI 3.1.1.

published 2017-09-05 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11951

cvss
7.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

An exploitable use-after-free vulnerability exists in the account parsing component of the Ledger-CLI 3.1.1. A specially crafted ledger file can cause a use-after-free vulnerability resulting in arbitrary code execution. An attacker can convince a user to load a journal file to trigger this vulnerability.

Patch / fix

  • ledger Debian 14, Debian 13, Debian 12 3.1.2+dfsg1-1

debian advisories DEBIAN-CVE-2017-2808

  • ledger openSUSE Tumbleweed 3.2.1-3.3
  • ledger Package Hub 15 SP1 3.1.3-bp151.4.3.1
  • ledger openSUSE Leap 15.1, openSUSE Leap 15.0 3.1.3-lp151.3.3.1

opensuse advisories openSUSE-SU-2024:10913-1openSUSE-SU-2019:1895-1openSUSE-SU-2019:1779-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-2017-2808 updated cvss 7.5

ledger: CLI Account Directive Use-After-Free 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

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

CVSS scores

assigned by version score vector
CNA 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.0 7.8 CVSS:3.0/AV:L/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

Affected products

  • Ledger Ledger CLI

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.