CVE-2020-35448
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed...
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
3.3
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
CVE-2020-35448- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:P/I:N/A:N - Weakness
- CWE-125
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
CVE-2020-35448- Updated
- 2026-11-02
EUVDEUVD-2020-23122 No score
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
EUVD-2020-23122- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-r2cj-jqqc-j833
3.3
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed...
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
GHSA-r2cj-jqqc-j833- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - Weakness
- CWE-125, CWE-787
- Updated
- 2026-11-02
OSVALPINE-CVE-2020-35448
3.3
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
ALPINE-CVE-2020-35448- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - Updated
- 2026-11-03
OSVBELL-CVE-2020-35448
3.3
CVE-2020-35448 does not affect BellSoft software
- Record
BELL-CVE-2020-35448- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
Show 12 moreShow less
OSV
3.3
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
CVE-2020-35448- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
OSVDEBIAN-CVE-2020-35448
3.3
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.
- Record
DEBIAN-CVE-2020-35448- CVSS 3.1
- 3.3 Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
OSVRHSA-2021:4364
4.7
Red Hat Security Advisory: binutils security update
- Record
RHSA-2021:4364- CVSS 3.1
- 4.7 Medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2021:4364
6.5
Moderate: binutils security update
The binutils packages provide a collection of binary utilities for the manipulation of object code in various object file formats. It includes the ar, as, gprof, ld, nm, objcopy, objdump, ranlib, readelf, size, strings, strip, and addr2line utilities.
Security Fix(es):
-
binutils: Excessive debug section size can cause excessive memory consumption in bfd's dwarf2.c read_section() (CVE-2021-3487)
-
binutils: Race window allows users to own arbitrary files (CVE-2021-20197)
-
binutils: Heap-based buffer overflow in bfd_getl_signed_32() in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section() in elf.c (CVE-2020-35448)
-
binutils: Heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_section in elf.c (CVE-2021-20284)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the Rocky Linux 8.5 Release Notes linked from the References section.
- Record
RLSA-2021:4364- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVALSA-2021:4364 No score
Moderate: binutils security update
The binutils packages provide a collection of binary utilities for the manipulation of object code in various object file formats. It includes the ar, as, gprof, ld, nm, objcopy, objdump, ranlib, readelf, size, strings, strip, and addr2line utilities.
Security Fix(es):
-
binutils: Excessive debug section size can cause excessive memory consumption in bfd's dwarf2.c read_section() (CVE-2021-3487)
-
binutils: Race window allows users to own arbitrary files (CVE-2021-20197)
-
binutils: Heap-based buffer overflow in bfd_getl_signed_32() in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section() in elf.c (CVE-2020-35448)
-
binutils: Heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_section in elf.c (CVE-2021-20284)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.
- Record
ALSA-2021:4364- Updated
- 2026-11-02
OSVCLSA-2022-1645466518 No score
Fix of CVE: CVE-2021-20284, CVE-2021-20197, CVE-2021-42574, CVE-2021-3487, CVE-2020-35448
- CVE-2021-42574: Developer environment: Unicode's bidirectional (BiDi) override characters can cause trojan source attacks (#2009172)
- CVE-2021-20284: Heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_section in elf.c (#1961526)
- CVE-2020-35448: Heap-based buffer overflow in bfd_getl_signed_32() in libbfd.c (#1953659)
- CVE-2021-3487: Excessive debug section size can cause excessive memory consumption in bfd's dwarf2.c read_section() (#1947134)
- CVE-2021-20197: Race window allows users to own arbitrary files (#1920642)
- Record
CLSA-2022-1645466518- Updated
- 2026-11-02
OSVopenSUSE-SU-2021:1475-1 No score
Security update for binutils
This update for binutils fixes the following issues:
Update to binutils 2.37:
-
The GNU Binutils sources now requires a C99 compiler and library to build.
-
Support for Realm Management Extension (RME) for AArch64 has been added.
-
A new linker option '-z report-relative-reloc' for x86 ELF targets has been added to report dynamic relative relocations.
-
A new linker option '-z start-stop-gc' has been added to disable special treatment of _start/_stop references when --gc-sections.
-
A new linker options '-Bno-symbolic' has been added which will cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
-
The readelf tool has a new command line option which can be used to specify how the numeric values of symbols are reported. --sym-base=0|8|10|16 tells readelf to display the values in base 8, base 10 or base 16. A sym base of 0 represents the default action of displaying values under 10000 in base 10 and values above that in base 16.
-
A new format has been added to the nm program. Specifying '--format=just-symbols' (or just using -j) will tell the program to only display symbol names and nothing else.
-
A new command line option '--keep-section-symbols' has been added to objcopy and strip. This stops the removal of unused section symbols when the file is copied. Removing these symbols saves space, but sometimes they are needed by other tools.
-
The '--weaken', '--weaken-symbol' and '--weaken-symbols' options supported by objcopy now make undefined symbols weak on targets that support weak symbols.
-
Readelf and objdump can now display and use the contents of .debug_sup sections.
-
Readelf and objdump will now follow links to separate debug info files by default. This behaviour can be stopped via the use of the new '-wN' or '--debug-dump=no-follow-links' options for readelf and the '-WN' or '--dwarf=no-follow-links' options for objdump. Also the old behaviour can be restored by the use of the '--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly changed. When enabled, the option allows for the loading of symbol tables and string tables from the separate files which can be used to enhance the information displayed when dumping other sections, but it does not automatically imply that information from the separate files should be displayed.
If other debug section display options are also enabled (eg '--debug-dump=info') then the contents of matching sections in both the main file and the separate debuginfo file will be displayed. This is because in most cases the debug section will only be present in one of the files.
If however non-debug section display options are enabled (eg '--sections') then the contents of matching parts of the separate debuginfo file will not be displayed. This is because in most cases the user probably only wanted to load the symbol information from the separate debuginfo file. In order to change this behaviour a new command line option --process-links can be used. This will allow di0pslay options to applied to both the main file and any separate debuginfo files.
-
Nm has a new command line option: '--quiet'. This suppresses 'no symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
-
General:
- When setting the link order attribute of ELF sections, it is now possible to use a numeric section index instead of symbol name.
- Added a .nop directive to generate a single no-op instruction in a target neutral manner. This instruction does have an effect on DWARF line number generation, if that is active.
- Removed --reduce-memory-overheads and --hash-size as gas now uses hash tables that can be expand and shrink automatically.
-
X86/x86_64:
- Add support for AVX VNNI, HRESET, UINTR, TDX, AMX and Key Locker instructions.
- Support non-absolute segment values…
- Record
openSUSE-SU-2021:1475-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2021:3616-1 No score
Security update for binutils
This update for binutils fixes the following issues:
Update to binutils 2.37:
-
The GNU Binutils sources now requires a C99 compiler and library to build.
-
Support for Realm Management Extension (RME) for AArch64 has been added.
-
A new linker option '-z report-relative-reloc' for x86 ELF targets has been added to report dynamic relative relocations.
-
A new linker option '-z start-stop-gc' has been added to disable special treatment of _start/_stop references when --gc-sections.
-
A new linker options '-Bno-symbolic' has been added which will cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
-
The readelf tool has a new command line option which can be used to specify how the numeric values of symbols are reported. --sym-base=0|8|10|16 tells readelf to display the values in base 8, base 10 or base 16. A sym base of 0 represents the default action of displaying values under 10000 in base 10 and values above that in base 16.
-
A new format has been added to the nm program. Specifying '--format=just-symbols' (or just using -j) will tell the program to only display symbol names and nothing else.
-
A new command line option '--keep-section-symbols' has been added to objcopy and strip. This stops the removal of unused section symbols when the file is copied. Removing these symbols saves space, but sometimes they are needed by other tools.
-
The '--weaken', '--weaken-symbol' and '--weaken-symbols' options supported by objcopy now make undefined symbols weak on targets that support weak symbols.
-
Readelf and objdump can now display and use the contents of .debug_sup sections.
-
Readelf and objdump will now follow links to separate debug info files by default. This behaviour can be stopped via the use of the new '-wN' or '--debug-dump=no-follow-links' options for readelf and the '-WN' or '--dwarf=no-follow-links' options for objdump. Also the old behaviour can be restored by the use of the '--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly changed. When enabled, the option allows for the loading of symbol tables and string tables from the separate files which can be used to enhance the information displayed when dumping other sections, but it does not automatically imply that information from the separate files should be displayed.
If other debug section display options are also enabled (eg '--debug-dump=info') then the contents of matching sections in both the main file and the separate debuginfo file will be displayed. This is because in most cases the debug section will only be present in one of the files.
If however non-debug section display options are enabled (eg '--sections') then the contents of matching parts of the separate debuginfo file will not be displayed. This is because in most cases the user probably only wanted to load the symbol information from the separate debuginfo file. In order to change this behaviour a new command line option --process-links can be used. This will allow di0pslay options to applied to both the main file and any separate debuginfo files.
-
Nm has a new command line option: '--quiet'. This suppresses 'no symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
-
General:
- When setting the link order attribute of ELF sections, it is now possible to use a numeric section index instead of symbol name.
- Added a .nop directive to generate a single no-op instruction in a target neutral manner. This instruction does have an effect on DWARF line number generation, if that is active.
- Removed --reduce-memory-overheads and --hash-size as gas now uses hash tables that can be expand and shrink automatically.
-
X86/x86_64:
- Add support for AVX VNNI, HRESET, UINTR, TDX, AMX and Key Locker instructions.
- Support non-absolute segment values…
- Record
openSUSE-SU-2021:3616-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10651-1 No score
binutils-2.37-1.3 on GA media
These are all security issues fixed in the binutils-2.37-1.3 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10651-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:3593-1 No score
Security update for binutils
This update for binutils fixes the following issues:
Update to binutils 2.37:
-
The GNU Binutils sources now requires a C99 compiler and library to build.
-
Support for the arm-symbianelf format has been removed.
-
Support for Realm Management Extension (RME) for AArch64 has been added.
-
A new linker option '-z report-relative-reloc' for x86 ELF targets has been added to report dynamic relative relocations.
-
A new linker option '-z start-stop-gc' has been added to disable special treatment of _start/_stop references when --gc-sections.
-
A new linker options '-Bno-symbolic' has been added which will cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
-
The readelf tool has a new command line option which can be used to specify how the numeric values of symbols are reported. --sym-base=0|8|10|16 tells readelf to display the values in base 8, base 10 or base 16. A sym base of 0 represents the default action of displaying values under 10000 in base 10 and values above that in base 16.
-
A new format has been added to the nm program. Specifying '--format=just-symbols' (or just using -j) will tell the program to only display symbol names and nothing else.
-
A new command line option '--keep-section-symbols' has been added to objcopy and strip. This stops the removal of unused section symbols when the file is copied. Removing these symbols saves space, but sometimes they are needed by other tools.
-
The '--weaken', '--weaken-symbol' and '--weaken-symbols' options supported by objcopy now make undefined symbols weak on targets that support weak symbols.
-
Readelf and objdump can now display and use the contents of .debug_sup sections.
-
Readelf and objdump will now follow links to separate debug info files by default. This behaviour can be stopped via the use of the new '-wN' or '--debug-dump=no-follow-links' options for readelf and the '-WN' or '--dwarf=no-follow-links' options for objdump. Also the old behaviour can be restored by the use of the '--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly changed. When enabled, the option allows for the loading of symbol tables and string tables from the separate files which can be used to enhance the information displayed when dumping other sections, but it does not automatically imply that information from the separate files should be displayed.
If other debug section display options are also enabled (eg '--debug-dump=info') then the contents of matching sections in both the main file and the separate debuginfo file will be displayed. This is because in most cases the debug section will only be present in one of the files.
If however non-debug section display options are enabled (eg '--sections') then the contents of matching parts of the separate debuginfo file will not be displayed. This is because in most cases the user probably only wanted to load the symbol information from the separate debuginfo file. In order to change this behaviour a new command line option --process-links can be used. This will allow di0pslay options to applied to both the main file and any separate debuginfo files.
-
Nm has a new command line option: '--quiet'. This suppresses 'no symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
General:
- When setting the link order attribute of ELF sections, it is now possible to use a numeric section index instead of symbol name.
- Added a .nop directive to generate a single no-op instruction in a target neutral manner. This instruction does have an effect on DWARF line number generation, if that is active.
- Removed --reduce-memory-overheads and --hash-size as gas now uses hash tables that can be expand and shrink automatically.
X86/x86_64:
* Add support for AVX VNNI, HRESET, UINTR, TDX, AMX and Key
…
- Record
SUSE-SU-2021:3593-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:3616-1 No score
Security update for binutils
This update for binutils fixes the following issues:
Update to binutils 2.37:
-
The GNU Binutils sources now requires a C99 compiler and library to build.
-
Support for Realm Management Extension (RME) for AArch64 has been added.
-
A new linker option '-z report-relative-reloc' for x86 ELF targets has been added to report dynamic relative relocations.
-
A new linker option '-z start-stop-gc' has been added to disable special treatment of _start/_stop references when --gc-sections.
-
A new linker options '-Bno-symbolic' has been added which will cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
-
The readelf tool has a new command line option which can be used to specify how the numeric values of symbols are reported. --sym-base=0|8|10|16 tells readelf to display the values in base 8, base 10 or base 16. A sym base of 0 represents the default action of displaying values under 10000 in base 10 and values above that in base 16.
-
A new format has been added to the nm program. Specifying '--format=just-symbols' (or just using -j) will tell the program to only display symbol names and nothing else.
-
A new command line option '--keep-section-symbols' has been added to objcopy and strip. This stops the removal of unused section symbols when the file is copied. Removing these symbols saves space, but sometimes they are needed by other tools.
-
The '--weaken', '--weaken-symbol' and '--weaken-symbols' options supported by objcopy now make undefined symbols weak on targets that support weak symbols.
-
Readelf and objdump can now display and use the contents of .debug_sup sections.
-
Readelf and objdump will now follow links to separate debug info files by default. This behaviour can be stopped via the use of the new '-wN' or '--debug-dump=no-follow-links' options for readelf and the '-WN' or '--dwarf=no-follow-links' options for objdump. Also the old behaviour can be restored by the use of the '--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly changed. When enabled, the option allows for the loading of symbol tables and string tables from the separate files which can be used to enhance the information displayed when dumping other sections, but it does not automatically imply that information from the separate files should be displayed.
If other debug section display options are also enabled (eg '--debug-dump=info') then the contents of matching sections in both the main file and the separate debuginfo file will be displayed. This is because in most cases the debug section will only be present in one of the files.
If however non-debug section display options are enabled (eg '--sections') then the contents of matching parts of the separate debuginfo file will not be displayed. This is because in most cases the user probably only wanted to load the symbol information from the separate debuginfo file. In order to change this behaviour a new command line option --process-links can be used. This will allow di0pslay options to applied to both the main file and any separate debuginfo files.
-
Nm has a new command line option: '--quiet'. This suppresses 'no symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
-
General:
- When setting the link order attribute of ELF sections, it is now possible to use a numeric section index instead of symbol name.
- Added a .nop directive to generate a single no-op instruction in a target neutral manner. This instruction does have an effect on DWARF line number generation, if that is active.
- Removed --reduce-memory-overheads and --hash-size as gas now uses hash tables that can be expand and shrink automatically.
-
X86/x86_64:
- Add support for AVX VNNI, HRESET, UINTR, TDX, AMX and Key Locker instructions.
- Support non-absolute segment values…
- Record
SUSE-SU-2021:3616-1- Updated
- 2026-11-02
OSVSUSE-SU-2022:0934-1 No score
Security update for binutils
This update for binutils fixes the following issues:
- For compatibility on old code stream that expect 'brcl 0,label' to not be disassembled as 'jgnop label' on s390x. (bsc#1192267) This reverts IBM zSeries HLASM support for now.
- Fixed that ppc64 optflags did not enable LTO (bsc#1188941).
- Fix empty man-pages from broken release tarball
- Fixed a memory corruption with rpath option (bsc#1191473).
- Fixed slow performance of stripping some binaries (bsc#1183909).
Update to binutils 2.37:
-
The GNU Binutils sources now requires a C99 compiler and library to build.
-
Support for Realm Management Extension (RME) for AArch64 has been added.
-
A new linker option '-z report-relative-reloc' for x86 ELF targets has been added to report dynamic relative relocations.
-
A new linker option '-z start-stop-gc' has been added to disable special treatment of _start/_stop references when --gc-sections.
-
A new linker options '-Bno-symbolic' has been added which will cancel the '-Bsymbolic' and '-Bsymbolic-functions' options.
-
The readelf tool has a new command line option which can be used to specify how the numeric values of symbols are reported. --sym-base=0|8|10|16 tells readelf to display the values in base 8, base 10 or base 16. A sym base of 0 represents the default action of displaying values under 10000 in base 10 and values above that in base 16.
-
A new format has been added to the nm program. Specifying '--format=just-symbols' (or just using -j) will tell the program to only display symbol names and nothing else.
-
A new command line option '--keep-section-symbols' has been added to objcopy and strip. This stops the removal of unused section symbols when the file is copied. Removing these symbols saves space, but sometimes they are needed by other tools.
-
The '--weaken', '--weaken-symbol' and '--weaken-symbols' options supported by objcopy now make undefined symbols weak on targets that support weak symbols.
-
Readelf and objdump can now display and use the contents of .debug_sup sections.
-
Readelf and objdump will now follow links to separate debug info files by default. This behaviour can be stopped via the use of the new '-wN' or '--debug-dump=no-follow-links' options for readelf and the '-WN' or '--dwarf=no-follow-links' options for objdump. Also the old behaviour can be restored by the use of the '--enable-follow-debug-links=no' configure time option.
The semantics of the =follow-links option have also been slightly changed. When enabled, the option allows for the loading of symbol tables and string tables from the separate files which can be used to enhance the information displayed when dumping other sections, but it does not automatically imply that information from the separate files should be displayed.
If other debug section display options are also enabled (eg '--debug-dump=info') then the contents of matching sections in both the main file and the separate debuginfo file will be displayed. This is because in most cases the debug section will only be present in one of the files.
If however non-debug section display options are enabled (eg '--sections') then the contents of matching parts of the separate debuginfo file will not be displayed. This is because in most cases the user probably only wanted to load the symbol information from the separate debuginfo file. In order to change this behaviour a new command line option --process-links can be used. This will allow di0pslay options to applied to both the main file and any separate debuginfo files.
-
Nm has a new command line option: '--quiet'. This suppresses 'no symbols' diagnostic.
Update to binutils 2.36:
New features in the Assembler:
-
General:
- When setting the link order attribute of ELF sections, it is now possible to use a numeric section index instead of symbol name.
- Added a .nop directive to generate a single…
- Record
SUSE-SU-2022:0934-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
binutils-cross-embeddedAlpine:v3.15 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.16 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.17 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.18 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.19 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.20 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.21 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.22 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.23 |
before 2.37-r0 | 2.37-r0 |
binutils-cross-embeddedAlpine:v3.24 |
before 2.37-r0 | 2.37-r0 |
Show 104 moreShow less
| Package | Affected | Fixed |
|---|---|---|
mingw-w64-binutilsAlpine:v3.14 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.15 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.16 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.17 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.18 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.19 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.20 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.21 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.22 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.23 |
before 2.36-r0 | 2.36-r0 |
mingw-w64-binutilsAlpine:v3.24 |
before 2.36-r0 | 2.36-r0 |
binutils-develAlmaLinux:8 From an advisory covering 4 CVEs |
before 2.30-108.el8 | 2.30-108.el8 |
binutilsTuxCare:CentOS:8.4 From an advisory covering 5 CVEs |
before 2.30-93.el8.4.tuxcare.els1 | 2.30-93.el8.4.tuxcare.els1 |
binutils-develTuxCare:CentOS:8.4 From an advisory covering 5 CVEs |
before 2.30-93.el8.4.tuxcare.els1 | 2.30-93.el8.4.tuxcare.els1 |
binutilsDebian:12 |
before 2.37-3 | 2.37-3 |
binutilsDebian:13 |
before 2.37-3 | 2.37-3 |
binutilsDebian:14 |
before 2.37-3 | 2.37-3 |
binutils-debuginfoRed Hat:enterprise_linux:8::appstream From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutils-debugsourceRed Hat:enterprise_linux:8::appstream From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutils-develRed Hat:enterprise_linux:8::appstream From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutilsRed Hat:enterprise_linux:8::baseos From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutils-debuginfoRed Hat:enterprise_linux:8::baseos From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutils-debugsourceRed Hat:enterprise_linux:8::baseos From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutilsRocky Linux:8 From an advisory covering 4 CVEs |
before 0:2.30-108.el8 | 0:2.30-108.el8 |
binutilsSUSE:HPE Helion OpenStack 8 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:OpenStack Cloud 8 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:OpenStack Cloud 9 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:OpenStack Cloud Crowbar 8 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:OpenStack Cloud Crowbar 9 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server for SAP Applications 12 SP3 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
cross-ppc-binutilsSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
cross-spu-binutilsSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server 12 SP2-BCL From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server 12 SP3-LTSS From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server 12 SP3-BCL From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server 12 SP4-LTSS From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server 12 SP5 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Server for SAP Applications 12 SP5 From an advisory covering 21 CVEs |
before 2.37-9.39.1 | 2.37-9.39.1 |
binutilsSUSE:Linux Enterprise Module for Basesystem 15 SP2 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Module for Development Tools 15 SP2 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
bpftraceSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 13 CVEs |
before 0.11.4-3.2.1 | 0.11.4-3.2.1 |
binutilsSUSE:Linux Enterprise Module for Package Hub 15 SP2 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Module for Package Hub 15 SP3 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Enterprise Storage 6 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
binutilsSUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 14 CVEs |
before 2.37-6.23.1 | 2.37-6.23.1 |
binutilsSUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 14 CVEs |
before 2.37-6.23.1 | 2.37-6.23.1 |
binutilsSUSE:Linux Enterprise Server 15-LTSS From an advisory covering 14 CVEs |
before 2.37-6.23.1 | 2.37-6.23.1 |
binutilsSUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 14 CVEs |
before 2.37-6.23.1 | 2.37-6.23.1 |
binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
bpftraceopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 0.11.4-lp152.2.7.1 | 0.11.4-lp152.2.7.1 |
cross-aarch64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-arm-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-avr-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-epiphany-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-hppa-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-hppa64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-i386-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-ia64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-m68k-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-mips-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-ppc-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-ppc64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-ppc64le-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-riscv64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-rx-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-s390-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-s390x-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-sparc-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-sparc64-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-spu-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
cross-xtensa-binutilsopenSUSE:Leap 15.2 From an advisory covering 14 CVEs |
before 2.37-lp152.4.9.1 | 2.37-lp152.4.9.1 |
binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.2 | 2.37-7.21.2 |
bpftraceopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 0.11.4-3.2.1 | 0.11.4-3.2.1 |
cross-aarch64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-arm-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-avr-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-epiphany-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-hppa-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-hppa64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-i386-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-ia64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-m68k-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-mips-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-ppc-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-ppc64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-ppc64le-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-riscv64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-rx-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-s390-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-s390x-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-sparc-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-sparc64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-spu-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
cross-x86_64-binutilsopenSUSE:Leap 15.3 From an advisory covering 13 CVEs |
before 2.37-7.21.1 | 2.37-7.21.1 |
binutilsopenSUSE:Tumbleweed From an advisory covering 106 CVEs |
before 2.37-1.3 | 2.37-1.3 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected, aliases, references | OSV | |
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-35448 is a low vulnerability (CVSS 3.3) in Gnu Binutils, published December 27, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.24%, the 69th percentile. Fixed in binutils-cross-embedded 2.37-r0.
References
sourceware.org/bugzilla/show_bug.cgi?id=26574
sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=8642dafaef21aa6747cec01df1977e9c52eb4679
security.netapp.com/advisory/ntap-20210129-0008
security.gentoo.org/glsa/202107-24
nvd.nist.gov/vuln/detail/CVE-2020-35448
sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8642dafaef21aa6747cec01df1977e9c52eb4679
Show 181 moreShow less
github.com/advisories/GHSA-r2cj-jqqc-j833
security.alpinelinux.org/vuln/CVE-2020-35448
vulners.com/cve/CVE-2020-35448
vulners.com/cve/CVE-2021-20197
vulners.com/cve/CVE-2021-20284
vulners.com/cve/CVE-2021-3487
docs.bell-sw.com/security/cves/CVE-2020-35448
errata.cloudlinux.com/centos8.4-els/CLSA-2022-1645466518.html
security-tracker.debian.org/tracker/CVE-2020-35448
access.redhat.com/errata/RHSA-2021:4364
access.redhat.com/security/updates/classification
access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.5_release_notes
bugzilla.redhat.com/show_bug.cgi?id=1913743
bugzilla.redhat.com/show_bug.cgi?id=1924068
bugzilla.redhat.com/show_bug.cgi?id=1930988
bugzilla.redhat.com/show_bug.cgi?id=1935785
bugzilla.redhat.com/show_bug.cgi?id=1937784
bugzilla.redhat.com/show_bug.cgi?id=1946518
bugzilla.redhat.com/show_bug.cgi?id=1946977
bugzilla.redhat.com/show_bug.cgi?id=1947111
bugzilla.redhat.com/show_bug.cgi?id=1950478
bugzilla.redhat.com/show_bug.cgi?id=1969775
security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_4364.json
access.redhat.com/security/cve/CVE-2020-35448
cve.org/CVERecord?id=CVE-2020-35448
access.redhat.com/security/cve/CVE-2021-3487
cve.org/CVERecord?id=CVE-2021-3487
nvd.nist.gov/vuln/detail/CVE-2021-3487
access.redhat.com/security/cve/CVE-2021-20197
cve.org/CVERecord?id=CVE-2021-20197
nvd.nist.gov/vuln/detail/CVE-2021-20197
access.redhat.com/security/cve/CVE-2021-20284
cve.org/CVERecord?id=CVE-2021-20284
nvd.nist.gov/vuln/detail/CVE-2021-20284
errata.rockylinux.org/RLSA-2021:4364
suse.com/support/update/announcement/2021/suse-su-20213593-1
bugzilla.suse.com/1126826
bugzilla.suse.com/1126829
bugzilla.suse.com/1126831
bugzilla.suse.com/1140126
bugzilla.suse.com/1142649
bugzilla.suse.com/1143609
bugzilla.suse.com/1153768
bugzilla.suse.com/1153770
bugzilla.suse.com/1157755
bugzilla.suse.com/1160254
bugzilla.suse.com/1160590
bugzilla.suse.com/1163333
bugzilla.suse.com/1163744
bugzilla.suse.com/1179036
bugzilla.suse.com/1179341
bugzilla.suse.com/1179898
bugzilla.suse.com/1179899
bugzilla.suse.com/1179900
bugzilla.suse.com/1179901
bugzilla.suse.com/1179902
bugzilla.suse.com/1179903
bugzilla.suse.com/1180451
bugzilla.suse.com/1180454
bugzilla.suse.com/1180461
bugzilla.suse.com/1181452
bugzilla.suse.com/1182252
bugzilla.suse.com/1183511
bugzilla.suse.com/1184620
bugzilla.suse.com/1184794
suse.com/security/cve/CVE-2019-12972
suse.com/security/cve/CVE-2019-14250
suse.com/security/cve/CVE-2019-14444
suse.com/security/cve/CVE-2019-17450
suse.com/security/cve/CVE-2019-17451
suse.com/security/cve/CVE-2019-9074
suse.com/security/cve/CVE-2019-9075
suse.com/security/cve/CVE-2019-9077
suse.com/security/cve/CVE-2020-16590
suse.com/security/cve/CVE-2020-16591
suse.com/security/cve/CVE-2020-16592
suse.com/security/cve/CVE-2020-16593
suse.com/security/cve/CVE-2020-16598
suse.com/security/cve/CVE-2020-16599
suse.com/security/cve/CVE-2020-35448
suse.com/security/cve/CVE-2020-35493
suse.com/security/cve/CVE-2020-35496
suse.com/security/cve/CVE-2020-35507
suse.com/security/cve/CVE-2021-20197
suse.com/security/cve/CVE-2021-20284
suse.com/security/cve/CVE-2021-3487
suse.com/support/update/announcement/2021/suse-su-20213616-1
suse.com/support/update/announcement/2022/suse-su-20220934-1
bugzilla.suse.com/1183909
bugzilla.suse.com/1184519
bugzilla.suse.com/1188941
bugzilla.suse.com/1191473
bugzilla.suse.com/1192267
suse.com/security/cve/CVE-2021-20294
lists.opensuse.org/archives/list/[email protected]/thread/N6RYWEZ5BKTK6UEP6HAB7B466BPC3SMJ
lists.opensuse.org/archives/list/[email protected]/thread/4TQ3DLF5YEQDDJUON6WGBX2HVVM7FOLB
suse.com/security/cve/CVE-2014-9939
suse.com/security/cve/CVE-2017-12448
suse.com/security/cve/CVE-2017-12450
suse.com/security/cve/CVE-2017-12452
suse.com/security/cve/CVE-2017-12453
suse.com/security/cve/CVE-2017-12454
suse.com/security/cve/CVE-2017-12456
suse.com/security/cve/CVE-2017-12799
suse.com/security/cve/CVE-2017-13757
suse.com/security/cve/CVE-2017-14128
suse.com/security/cve/CVE-2017-14129
suse.com/security/cve/CVE-2017-14130
suse.com/security/cve/CVE-2017-14333
suse.com/security/cve/CVE-2017-14529
suse.com/security/cve/CVE-2017-14729
suse.com/security/cve/CVE-2017-14745
suse.com/security/cve/CVE-2017-14974
suse.com/security/cve/CVE-2017-15938
suse.com/security/cve/CVE-2017-15939
suse.com/security/cve/CVE-2017-15996
suse.com/security/cve/CVE-2017-16826
suse.com/security/cve/CVE-2017-16827
suse.com/security/cve/CVE-2017-16828
suse.com/security/cve/CVE-2017-16829
suse.com/security/cve/CVE-2017-16830
suse.com/security/cve/CVE-2017-16831
suse.com/security/cve/CVE-2017-16832
suse.com/security/cve/CVE-2017-6965
suse.com/security/cve/CVE-2017-6966
suse.com/security/cve/CVE-2017-6969
suse.com/security/cve/CVE-2017-7209
suse.com/security/cve/CVE-2017-7210
suse.com/security/cve/CVE-2017-7223
suse.com/security/cve/CVE-2017-7224
suse.com/security/cve/CVE-2017-7225
suse.com/security/cve/CVE-2017-7226
suse.com/security/cve/CVE-2017-7299
suse.com/security/cve/CVE-2017-7300
suse.com/security/cve/CVE-2017-7301
suse.com/security/cve/CVE-2017-7302
suse.com/security/cve/CVE-2017-7303
suse.com/security/cve/CVE-2017-7304
suse.com/security/cve/CVE-2017-8392
suse.com/security/cve/CVE-2017-8393
suse.com/security/cve/CVE-2017-8394
suse.com/security/cve/CVE-2017-8396
suse.com/security/cve/CVE-2017-8421
suse.com/security/cve/CVE-2017-9746
suse.com/security/cve/CVE-2017-9747
suse.com/security/cve/CVE-2017-9748
suse.com/security/cve/CVE-2017-9750
suse.com/security/cve/CVE-2017-9755
suse.com/security/cve/CVE-2017-9756
suse.com/security/cve/CVE-2018-1000876
suse.com/security/cve/CVE-2018-10372
suse.com/security/cve/CVE-2018-10373
suse.com/security/cve/CVE-2018-10534
suse.com/security/cve/CVE-2018-10535
suse.com/security/cve/CVE-2018-17358
suse.com/security/cve/CVE-2018-17359
suse.com/security/cve/CVE-2018-17360
suse.com/security/cve/CVE-2018-17985
suse.com/security/cve/CVE-2018-18309
suse.com/security/cve/CVE-2018-18483
suse.com/security/cve/CVE-2018-18484
suse.com/security/cve/CVE-2018-18605
suse.com/security/cve/CVE-2018-18606
suse.com/security/cve/CVE-2018-18607
suse.com/security/cve/CVE-2018-19931
suse.com/security/cve/CVE-2018-19932
suse.com/security/cve/CVE-2018-20623
suse.com/security/cve/CVE-2018-20651
suse.com/security/cve/CVE-2018-20671
suse.com/security/cve/CVE-2018-6323
suse.com/security/cve/CVE-2018-6543
suse.com/security/cve/CVE-2018-6759
suse.com/security/cve/CVE-2018-6872
suse.com/security/cve/CVE-2018-7208
suse.com/security/cve/CVE-2018-7568
suse.com/security/cve/CVE-2018-7569
suse.com/security/cve/CVE-2018-7570
suse.com/security/cve/CVE-2018-7642
suse.com/security/cve/CVE-2018-7643
suse.com/security/cve/CVE-2018-8945
suse.com/security/cve/CVE-2019-1010180
Left out here: the rest of 5 source descriptions. The JSON record has them.