Skip to content
Fencer Intel
medium 5.5

CVE-2020-35496 json

There's a flaw in bfd_pef_scan_start_address() of bfd/pef.c in binutils which could allow an attacker who is able to submit a crafted file…

published 5y ago modified last mo. also EUVD-2020-23165

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

There's a flaw in bfd_pef_scan_start_address() of bfd/pef.c in binutils which could allow an attacker who is able to submit a crafted file to be processed by objdump to cause a NULL pointer dereference. The greatest threat of this flaw is to application availability. This flaw affects binutils versions prior to 2.34.

Patch / fix

  • gnu binutils 2.34
  • binutils Debian 14, Debian 13, Debian 12 2.33.50.20200107-1

debian advisories DEBIAN-CVE-2020-35496

  • binutils SLES for SAP 15, SLES 15-LTSS, SLE High Performance Computing 15-LTSS +1 more 2.37-6.23.1
  • binutils SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLES 15 SP1-BCL +9 more 2.37-7.21.2
  • bpftrace SLE Module for Development Tools 15 SP3 0.11.4-3.2.1
  • binutils SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +11 more 2.37-9.39.1
  • cross-ppc-binutils SLE Software Development Kit 12 SP5 2.37-9.39.1
  • cross-spu-binutils SLE Software Development Kit 12 SP5 2.37-9.39.1

suse advisories SUSE-SU-2022:0934-1SUSE-SU-2021:3616-1SUSE-SU-2021:3593-1

  • binutils openSUSE Tumbleweed 2.37-1.3
  • binutils openSUSE Leap 15.2 2.37-lp152.4.9.1
  • bpftrace openSUSE Leap 15.2 0.11.4-lp152.2.7.1
  • cross-rx-binutils openSUSE Leap 15.2 2.37-lp152.4.9.1
  • cross-arm-binutils openSUSE Leap 15.2 2.37-lp152.4.9.1
  • cross-avr-binutils openSUSE Leap 15.2 2.37-lp152.4.9.1
  • cross-ppc-binutils openSUSE Leap 15.2 2.37-lp152.4.9.1
  • cross-spu-binutils openSUSE Leap 15.2 2.37-lp152.4.9.1

opensuse advisories openSUSE-SU-2024:10651-1openSUSE-SU-2021:1475-1openSUSE-SU-2021:3616-1

Is CVE-2020-35496 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2020-35496 updated cvss 5.5

binutils: NULL pointer dereference in bfd_pef_scan_start_address function in bfd/pef.c

  • Red Hat Enterprise Linux 6 binutils Red Hat Enterprise Linux 7 binutils
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 binutils, gcc-toolset-9-binutils
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 gcc-toolset-10-binutils Red Hat Enterprise Linux 9 binutils, binutils-gold
    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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1911444 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/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

Affected products

  • n/a binutils

Classification

Weakness

References

Sources

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.