CVE-2019-7560 json
Boolector use after free
published 2019-02-07 7 y ago modified 2026-06-17 4 mo ago also GHSA-g58x-799h-v9h6 , PYSEC-2019-252 , EUVD-2019-0164
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
In parser/btorsmt2.c in Boolector 3.0.0, opening a specially crafted input file leads to a use after free in get_failed_assumptions or btor_delete.
Patch / fix
- pypi pyboolector 3.1.0
Exploit prediction
0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Boolector/boolector/issues/29 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/Boolector/boolector/issues/28 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/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 |
| OSV | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyboolector | <3.1.0 |
3.1.0 |
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
github.com
/Boolector/boolector/issues/29
web, exploit, patch, third-party-advisory, report
-
github.com
/Boolector/boolector/issues/28
web, exploit, patch, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2019-7560
advisory
-
github.com
/boolector/boolector
package
-
github.com
/pypa/advisory-database/tree/main/vulns/pyboolector/PYSEC-2019-252.yaml
web
Sources
- CVE List CVE-2019-7560
- GitHub Advisory GHSA-g58x-799h-v9h6
- NVD CVE-2019-7560
- OSV PYSEC-2019-252
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.