binutils: heap use after free in bfd_cache_close function
Published Aug 4, 2017
7.8
HIGHCVSS 3.0
EPSS 1.99%
Description
The bfd_cache_close function in bfd/cache.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause a heap use after free and possibly achieve code execution via a crafted nested archive file. This issue occurs because incorrect functions are called during an attempt to release memory. The issue can be addressed by better input validation in the bfd_generic_archive_p function in bfd/archive.c.
Affected products
No data.
No data.
Red Hat Enterprise Linux 5
binutils
Not affected
Red Hat Enterprise Linux 6
binutils
Not affected
Red Hat Enterprise Linux 7
binutils
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | binutils | Not affected | n/a |
| Red Hat Enterprise Linux 6 | binutils | Not affected | n/a |
| Red Hat Enterprise Linux 7 | binutils | Not affected | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
1 other source (Red Hat) ▾
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
AV:N/AC:M/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (25 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 1.99% (0.01989) | 79.88th | v5 (v2026.06.15) |
| Jun 15, 2026 | 1.91% (0.01910) | 77.04th | v5 (v2026.06.15) |
| Mar 30, 2025 | 1.40% (0.01401) | 78.67th | v4 (v2025.03.14) |
| Mar 29, 2025 | 3.68% (0.03678) | 79.58th | v4 (v2025.03.14) |
| Jul 20, 2024 | 0.17% (0.00166) | 53.69th | v3 (v2023.03.01) |
| May 10, 2024 | 0.17% (0.00166) | 52.97th | v3 (v2023.03.01) |
| Apr 25, 2024 | 0.16% (0.00159) | 51.80th | v3 (v2023.03.01) |
| Mar 15, 2024 | 0.13% (0.00133) | 47.46th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.12% (0.00119) | 44.70th | v3 (v2023.03.01) |
| Dec 20, 2023 | 0.67% (0.00673) | 77.59th | v3 (v2023.03.01) |
| Nov 8, 2023 | 0.70% (0.00705) | 78.09th | v3 (v2023.03.01) |
| Aug 20, 2023 | 0.47% (0.00468) | 72.41th | v3 (v2023.03.01) |
| Jul 15, 2023 | 0.41% (0.00412) | 70.51th | v3 (v2023.03.01) |
| Jun 14, 2023 | 0.25% (0.00246) | 61.23th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.20% (0.00200) | 56.05th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.64% (0.01639) | 75.92th | v2 (v2022.01.01) |
| Sep 3, 2022 | 1.64% (0.01639) | 74.92th | v2 (v2022.01.01) |
| Jun 30, 2022 | 1.32% (0.01318) | 66.80th | v2 (v2022.01.01) |
| May 1, 2022 | 1.21% (0.01208) | 59.19th | v2 (v2022.01.01) |
| Apr 1, 2022 | 1.10% (0.01103) | 50.07th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.10% (0.01103) | 28.56th | v2 (v2022.01.01) |
| Feb 3, 2022 | 0.92% (0.00918) | 25.93th | v1 |
| Jan 6, 2022 | 0.92% (0.00918) | 25.29th | v1 |
| Sep 1, 2021 | 0.92% (0.00918) | 60.61th | v1 |
| Apr 14, 2021 | 0.92% (0.00918) | 0.00th | v1 |
References (5)
- https://access.redhat.com/security/cve/CVE-2017-12448 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1483581 Issue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2017-12448
- https://sourceware.org/bugzilla/show_bug.cgi?id=21787 x_refsource_MISCIssue TrackingPatchThird Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2017-12448
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2017-12448 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1483581 | Issue Tracking | |
| https://nvd.nist.gov/vuln/detail/CVE-2017-12448 | ||
| https://sourceware.org/bugzilla/show_bug.cgi?id=21787 | x_refsource_MISCIssue TrackingPatchThird Party Advisory | |
| https://www.cve.org/CVERecord?id=CVE-2017-12448 |
Change history (0)
No recorded changes yet.