CVE-2020-15904 json
bsdiff4 out-of-bounds write via patch file
published 6y ago modified 4mo ago also GHSA-f8m3-jpxr-hm5x , PYSEC-2020-30 , EUVD-2020-0058
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
A buffer overflow in the patching routine of bsdiff4 before 1.2.0 allows an attacker to write to heap memory (beyond allocated bounds) via a crafted patch file.
Patch / fix
Is CVE-2020-15904 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
1.05% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| 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 | bsdiff4 | <1.2.0 |
1.2.0 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/ilanschnell/bsdiff4/commit/49a4cee2feef7deaf9d89e5e793a8824930284d7
web, patch, third-party-advisory
-
github.com
/ilanschnell/bsdiff4/blob/master/CHANGELOG.txt
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15904
advisory
-
github.com
/ilanschnell/bsdiff4
package
-
github.com
/ilanschnell/bsdiff4/blob/9a84c2ee01f5ba0742d18c9f3b3d5244ae7fb302/CHANGELOG.txt#L30-L31
web
-
github.com
/pypa/advisory-database/tree/main/vulns/bsdiff4/PYSEC-2020-30.yaml
web
-
github.com
/advisories/GHSA-f8m3-jpxr-hm5x
advisory
Sources
- CVE List CVE-2020-15904
- GitHub Advisory GHSA-f8m3-jpxr-hm5x
- NVD CVE-2020-15904
- OSV PYSEC-2020-30
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.