CVE-2022-38495 json
LIEF vulnerable to heap based buffer overflow via print_binary function
published 4y ago modified 4mo ago also GHSA-42vg-2q93-fj6j , PYSEC-2022-276 , EUVD-2022-0140
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
LIEF commit 365a16a was discovered to contain a heap-buffer overflow via the function print_binary at /c/macho_reader.c.
Patch / fix
- pypi lief 0.12.1
Is CVE-2022-38495 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/lief-project/LIEF/issues/767 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | lief | <=0.12.1 <0.12.1 |
0.12.1 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/lief-project/LIEF/issues/767
web, exploit, issue-tracking, patch, third-party-advisory, report
-
github.com
/lief-project/LIEF/commit/0033b6312fd311b2e45e379c04a83d77c1e58578
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-38495
advisory
-
github.com
/lief-project/LIEF
package
-
github.com
/pypa/advisory-database/tree/main/vulns/lief/PYSEC-2022-276.yaml
web
-
github.com
/advisories/GHSA-42vg-2q93-fj6j
advisory
Sources
- CVE List CVE-2022-38495
- GitHub Advisory GHSA-42vg-2q93-fj6j
- NVD CVE-2022-38495
- OSV PYSEC-2022-276
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.