Docker digitalmarketplace/base:4.4.4-20190405T092712Z

Vulnerabilities

432 via 893 paths

Dependencies

213

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:9
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 134
  • 75
  • 223
Status
  • 432
  • 0
  • 0
OS binaries
  • 419
  • 13

high severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

In the coff_pointerize_aux function in coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, an index is not validated, which allows remote attackers to cause a denial of service (segmentation fault) or possibly have unspecified other impact via a crafted file, as demonstrated by objcopy of a COFF object.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The process_version_sections function in readelf.c in GNU Binutils 2.29 allows attackers to cause a denial of service (Integer Overflow, and hang because of a time-consuming loop) or possibly have unspecified other impact via a crafted binary file with invalid values of ent.vn_next, during "readelf -a" execution.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The elf_object_p function in elfcode.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, has an unsigned integer overflow because bfd_size_type multiplication is not used. A crafted ELF file allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The display_debug_ranges function in dwarf.c in GNU Binutils 2.30 allows remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact via a crafted ELF file, as demonstrated by objdump.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

In GNU Binutils 2.30, there's an integer overflow in the function load_specific_debug_section() in objdump.c, which results in malloc() with 0 size. A crafted ELF file allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The *_get_synthetic_symtab functions in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, interpret a -1 value as a sorting count instead of an error flag, which allows remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact via a crafted ELF file, related to elf32-i386.c and elf64-x86-64.c.

References

high severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, has a memory leak via a crafted string, leading to a denial of service (memory consumption), as demonstrated by cxxfilt, a related issue to CVE-2018-12698.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The bfd_make_section_with_flags function in section.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 NULL dereference via a crafted file.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The setup_group function in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a group section that is too small.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The elf_read_notesfunction in bfd/elf.c in GNU Binutils 2.29 allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The *_get_synthetic_symtab functions in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, do not ensure a unique PLT entry for a symbol, which allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted ELF file, related to elf32-i386.c and elf64-x86-64.c.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The evax_bfd_print_emh function in vms-alpha.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap read via a crafted vms alpha file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The _bfd_xcoff_read_ar_hdr function in bfd/coff-rs6000.c and bfd/coff64-rs6000.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds stack read via a crafted COFF image file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The bfd_mach_o_i386_canonicalize_one_reloc function in bfd/mach-o-i386.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap read via a crafted mach-o file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The _bfd_vms_slurp_eeom function in libbfd.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap read via a crafted vms alpha file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The _bfd_vms_slurp_egsd function in bfd/vms-alpha.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an arbitrary memory read via a crafted vms alpha file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The nlm_swap_auxiliary_headers_in function in bfd/nlmcode.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap read via a crafted nlm file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The read_symbol_stabs_debugging_info function in rddbg.c in GNU Binutils 2.29 and earlier allows remote attackers to cause an out of bounds heap read via a crafted binary file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The _bfd_vms_save_sized_string function in vms-misc.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap read via a crafted vms file.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The alpha_vms_object_p function in bfd/vms-alpha.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap write and possibly achieve code execution via a crafted vms alpha file.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The bfd_mach_o_read_symtab_strtab function in bfd/mach-o.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote attackers to cause an out of bounds heap write and possibly achieve code execution via a crafted mach-o file.

References

high severity

Use After Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

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.

References

high severity

Out-of-bounds Write

  • Vulnerable module: bzip2/libbz2-1.0
  • Introduced through: bzip2/libbz2-1.0@1.0.6-8.1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* bzip2/libbz2-1.0@1.0.6-8.1

Overview

BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

References

high severity

Arbitrary Code Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u11

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

Overview

Affected versions of this package are vulnerable to Arbitrary Code Injection curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.

Remediation

Upgrade curl to version or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

high severity

Double Free

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

high severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u13

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

Overview

Affected versions of this package are vulnerable to Improper Certificate Validation curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.

Remediation

Upgrade curl to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u13

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

Remediation

Upgrade curl to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

Overview

A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

References

high severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u12

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* curl/libcurl3-gnutls@7.52.1-5+deb9u9

Overview

Affected versions of this package are vulnerable to Use After Free. Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.

Remediation

Upgrade curl to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3 and cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3
  • Fixed in: 2.1.27~101-g0780600+dfsg-3+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3

Overview

cyrus-sasl (aka Cyrus SASL) 2.1.27 has an out-of-bounds write leading to unauthenticated remote denial-of-service in OpenLDAP via a malformed LDAP packet. The OpenLDAP crash is ultimately caused by an off-by-one error in _sasl_add_string in common.c in cyrus-sasl.

References

high severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.0-2+deb9u1
  • Fixed in: 2.2.0-2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* expat/libexpat1@2.2.0-2+deb9u1

Overview

In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.0-2+deb9u1
  • Fixed in: 2.2.0-2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* expat/libexpat1@2.2.0-2+deb9u1

Overview

In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable for denial-of-service attacks).

References

high severity

Information Exposure

  • Vulnerable module: gcc-6
  • Introduced through: gcc-6@6.3.0-18+deb9u1, gcc-6/cpp-6@6.3.0-18+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/cpp-6@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/gcc-6-base@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libasan3@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libatomic1@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libcc1-0@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libcilkrts5@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libgcc-6-dev@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libgcc1@1:6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libgomp1@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libitm1@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/liblsan0@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libmpx2@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libquadmath0@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libstdc++-6-dev@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libstdc++6@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libtsan0@6.3.0-18+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gcc-6/libubsan0@6.3.0-18+deb9u1

Overview

stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.

References

high severity

CVE-2019-1353

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. When running Git in the Windows Subsystem for Linux (also known as "WSL") while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.

References

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349, CVE-2019-1350, CVE-2019-1354, CVE-2019-1387.

References

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

References

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

References

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u6

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.3, 2.21.2, 2.22.3, 2.23.2, 2.24.2, 2.25.3, 2.26.1.

References

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* git/git-man@1:2.11.0-3+deb9u4

Overview

Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. This bug is similar to CVE-2020-5260(GHSA-qm7j-c969-7j4q). The fix for that bug still left the door open for an exploit where some credential is leaked (but the attacker cannot control which one). Git uses external "credential helper" programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that are considered illegal as of the recently published Git versions can cause Git to send a "blank" pattern to helpers, missing hostname and protocol fields. Many helpers will interpret this as matching any URL, and will return some unspecified stored password, leaking the password to an attacker's server. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The root of the problem is in Git itself, which should not be feeding blank input to helpers. However, the ability to exploit the vulnerability in practice depends on which helpers are in use. Credential helpers which are known to trigger the vulnerability: - Git's "store" helper - Git's "cache" helper - the "osxkeychain" helper that ships in Git's "contrib" directory Credential helpers which are known to be safe even with vulnerable versions of Git: - Git Credential Manager for Windows Any helper not in this list should be assumed to trigger the vulnerability.

References

high severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

In the GNU C Library (aka glibc or libc6) before 2.28, parse_reg_exp in posix/regcomp.c misparses alternatives, which allows attackers to cause a denial of service (assertion failure and application exit) or trigger an incorrect result by attempting a regular-expression match.

References

high severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

An integer overflow in the implementation of the posix_memalign in memalign functions in the GNU C Library (aka glibc or libc6) 2.26 and earlier could cause these functions to return a pointer to a heap area that is too small, potentially leading to heap corruption.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

In glibc 2.26 and earlier there is confusion in the usage of getcwd() by realpath() which can be used to write before the destination buffer leading to a buffer underflow and potential code execution.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

The malloc implementation in the GNU C Library (aka glibc or libc6), from version 2.24 to 2.26 on powerpc, and only in version 2.26 on i386, did not properly handle malloc calls with arguments close to SIZE_MAX and could return a pointer to a heap region that is smaller than requested, eventually leading to heap corruption.

References

high severity

Out-of-bounds Write

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

References

high severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

A use-after-free vulnerability introduced in glibc upstream version 2.14 was found in the way the tilde expansion was carried out. Directory paths containing an initial tilde followed by a valid username were affected by this issue. A local attacker could exploit this flaw by creating a specially crafted path that, when processed by the glob function, would potentially lead to arbitrary code execution. This was fixed in version 2.32.

References

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: gnupg2/gnupg
  • Introduced through: gnupg2/gnupg@2.1.18-8~deb9u4, gnupg2/gnupg-agent@2.1.18-8~deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gnupg2/gnupg@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gnupg2/gnupg-agent@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gnupg2/gpgv@2.1.18-8~deb9u4

Overview

GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060.

References

high severity

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.8-5+deb9u4
  • Fixed in: 3.5.8-5+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gnutls28/libgnutls30@3.5.8-5+deb9u4

Overview

A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7. A memory corruption (double free) vulnerability in the certificate verification API. Any client or server application that verifies X.509 certificates with GnuTLS 3.5.8 or later is affected.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: icu/icu-devtools
  • Introduced through: icu/icu-devtools@57.1-6+deb9u2, icu/libicu-dev@57.1-6+deb9u2 and others
  • Fixed in: 57.1-6+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* icu/icu-devtools@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* icu/libicu-dev@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* icu/libicu57@57.1-6+deb9u2

Overview

An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.

References

high severity

Uncontrolled Recursion

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.15-1+deb9u1, krb5/libk5crypto3@1.15-1+deb9u1 and others
  • Fixed in: 1.15-1+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5support0@1.15-1+deb9u1

Overview

Affected versions of this package are vulnerable to Uncontrolled Recursion. MIT Kerberos 5 (aka krb5) before 1.17.2 and 1.18.x before 1.18.3 allows unbounded recursion via an ASN.1-encoded Kerberos message because the lib/krb5/asn.1/asn1_encode.c support for BER indefinite lengths lacks a recursion limit.

Remediation

Upgrade krb5 to version or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libbsd/libbsd0
  • Introduced through: libbsd/libbsd0@0.8.3-1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libbsd/libbsd0@0.8.3-1

Overview

nlist.c in libbsd before 0.10.0 has an out-of-bounds read during a comparison for a symbol name from the string table (strtab).

References

high severity

Out-of-bounds Read

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.4-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libgd2/libgd3@2.2.4-2+deb9u4

Overview

** DISPUTED ** In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for development and testing purposes.'"

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libidn/libidn11
  • Introduced through: libidn/libidn11@1.33-1
  • Fixed in: 1.33-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libidn/libidn11@1.33-1

Overview

Integer overflow in the decode_digit function in puny_decode.c in Libidn2 before 2.0.4 allows remote attackers to cause a denial of service or possibly have unspecified other impact.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2
  • Fixed in: 1:1.5.1-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file.

Remediation

Upgrade libjpeg-turbo to version or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2
  • Fixed in: 1:1.5.1-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Overview

Affected versions of this package are vulnerable to Resource Exhaustion. In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption.

Remediation

Upgrade libjpeg-turbo to version or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.28-1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libpng1.6/libpng16-16@1.6.28-1

Overview

libpng before 1.6.32 does not properly check the length of chunks against the user limit.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH packets with a padding length value greater than the packet length are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the _libssh2_packet_require and _libssh2_packet_requirev functions. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a specially crafted SFTP packet is received from the server. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFTP packets with empty payloads are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit status message and no payload are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

In libssh2 before 1.9.0, kex_method_diffie_hellman_group_exchange_sha256_key_exchange in kex.c has an integer overflow that could lead to an out-of-bounds read in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server. This is related to an _libssh2_check_length mistake, and is different from the various issues fixed in 1.8.1, such as CVE-2019-3855.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

A flaw was found in libssh2 before 1.8.1. A server could send a multiple keyboard interactive response messages whose total length are greater than unsigned char max characters. This value is used as an index to copy memory causing in an out of bounds memory write error.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An integer overflow flaw, which could lead to an out of bounds write, was discovered in libssh2 before 1.8.1 in the way keyboard prompt requests are parsed. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way SSH_MSG_CHANNEL_REQUEST packets with an exit signal are parsed. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.7.0-1
  • Fixed in: 1.7.0-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libssh2/libssh2-1@1.7.0-1

Overview

An integer overflow flaw which could lead to an out of bounds write was discovered in libssh2 before 1.8.1 in the way packets are read from the server. A remote attacker who compromises a SSH server may be able to execute code on the client system when a user connects to the server.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.4-3+deb9u1 and libx11/libx11-data@2:1.6.4-3+deb9u1
  • Fixed in: 2:1.6.4-3+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libx11/libx11-6@2:1.6.4-3+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libx11/libx11-data@2:1.6.4-3+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. An integer overflow vulnerability leading to a double-free was found in libX11. This flaw allows a local privileged attacker to cause an application compiled with libX11 to crash, or in some cases, result in arbitrary code execution. The highest threat from this flaw is to confidentiality, integrity as well as system availability.

Remediation

Upgrade libx11 to version or higher.

References

high severity

Improper Resource Shutdown or Release

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.

References

high severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to newDoc->oldNs.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of service attack due to a crash of the application.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

The htmlParseTryOrFinish function in HTMLparser.c in libxml2 2.9.4 allows attackers to cause a denial of service (buffer over-read) or information disclosure.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted XML file.

References

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: libxslt/libxslt1-dev
  • Introduced through: libxslt/libxslt1-dev@1.1.29-2.1 and libxslt/libxslt1.1@1.1.29-2.1
  • Fixed in: 1.1.29-2.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1.1@1.1.29-2.1

Overview

In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.

References

high severity

Improper Access Control

  • Vulnerable module: libxslt/libxslt1-dev
  • Introduced through: libxslt/libxslt1-dev@1.1.29-2.1 and libxslt/libxslt1.1@1.1.29-2.1
  • Fixed in: 1.1.29-2.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1.1@1.1.29-2.1

Overview

libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon receiving a -1 error code. xsltCheckRead can return -1 for a crafted URL that is not actually invalid and is subsequently loaded.

References

high severity

Use After Free

  • Vulnerable module: libxslt/libxslt1-dev
  • Introduced through: libxslt/libxslt1-dev@1.1.29-2.1 and libxslt/libxslt1.1@1.1.29-2.1
  • Fixed in: 1.1.29-2.1+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1.1@1.1.29-2.1

Overview

In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclosed.

References

high severity

Use of Uninitialized Resource

  • Vulnerable module: libxslt/libxslt1-dev
  • Introduced through: libxslt/libxslt1-dev@1.1.29-2.1 and libxslt/libxslt1.1@1.1.29-2.1
  • Fixed in: 1.1.29-2.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxslt/libxslt1.1@1.1.29-2.1

Overview

In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.

References

high severity

CVE-2018-10754

  • Vulnerable module: ncurses/libncursesw5
  • Introduced through: ncurses/libncursesw5@6.0+20161126-1+deb9u2, ncurses/libtinfo5@6.0+20161126-1+deb9u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* ncurses/ncurses-bin@6.0+20161126-1+deb9u2

Overview

In ncurses before 6.1.20180414, there is a NULL Pointer Dereference in the _nc_parse_entry function of tinfo/parse_entry.c. It could lead to a remote denial of service if the terminfo library code is used to process untrusted terminfo data in which a use-name is invalid syntax. The product proceeds to the dereference code path even after a "dubious character `[' in name or alias field" detection.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.18.1-1
  • Fixed in: 1.18.1-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nghttp2/libnghttp2-14@1.18.1-1

Overview

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

References

high severity

Resource Exhaustion

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.18.1-1
  • Fixed in: 1.18.1-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nghttp2/libnghttp2-14@1.18.1-1

Overview

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others
  • Fixed in: 1.10.3-1+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-full@1.10.3-1+deb9u2

Overview

Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others
  • Fixed in: 1.10.3-1+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-full@1.10.3-1+deb9u2

Overview

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

References

high severity

HTTP Request Smuggling

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others
  • Fixed in: 1.10.3-1+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-full@1.10.3-1+deb9u2

Overview

An issue was discovered in OpenResty before 1.15.8.4. ngx_http_lua_subrequest.c allows HTTP request smuggling, as demonstrated by the ngx.location.capture API.

References

high severity

Resource Exhaustion

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others
  • Fixed in: 1.10.3-1+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-full@1.10.3-1+deb9u2

Overview

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

References

high severity

Arbitrary File Overwrite

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.17.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of packages that also create a serve binary would overwrite the first binary. This only affects files in /usr/local/bin.

For npm, this behaviour is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade node to version 12.14.0, 10.18.0, 8.17.0, 13.4.0 or higher.

References

high severity

Arbitrary File Write

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.17.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field.

For npm, a properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain access to arbitrary files on a user’s system when the package is installed. This behaviour is possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade node to version 12.14.0, 10.18.0, 8.17.0, 13.4.0 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). By using a combination of many requests with maximum sized headers (almost 80 KB per connection), and carefully timed completion of the headers, it is possible to cause the HTTP server to abort from heap allocation failure. Attack potential is mitigated by the use of a load balancer or other proxy layer.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 6.15.0, 8.14.0, 10.14.0, 11.3.0 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker could cause a Denial of Service (DoS) by sending headers very slowly keeping HTTP or HTTPS connections and associated resources alive for a long period of time.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 6.15.0, 8.14.0, 10.14.0, 11.3.0 or higher.

References

high severity

new

HTTP Request Smuggling

  • Vulnerable module: node
  • Introduced through: node@8.12.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to HTTP Request Smuggling. Two copies of a header field are allowed in a HTTP request, which causes Node.js to identifiy the first header and ignore the second.

Remediation

Upgrade node to version 10.23.1, 12.20.1, 14.15.4, 15.5.1 or higher.

References

high severity

Improper Authentication

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2
  • Fixed in: 2.4.44+dfsg-5+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Overview

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2
  • Fixed in: 2.4.44+dfsg-5+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. A NULL pointer dereference was found in OpenLDAP server and was fixed in openldap 2.4.55, during a request for renaming RDNs. An unauthenticated attacker could remotely crash the slapd process by sending a specially crafted request, causing a Denial of Service.

Remediation

Upgrade openldap to version or higher.

References

high severity

Resource Exhaustion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2
  • Fixed in: 2.4.44+dfsg-5+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Overview

In filter.c in slapd in OpenLDAP before 2.4.50, LDAP search filters with nested boolean expressions can result in denial of service (daemon crash).

References

high severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others
  • Fixed in: 1.1.0k-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl1.1@1.1.0j-1~deb9u1

Overview

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.3-2
  • Fixed in: 0.23.3-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* p11-kit/libp11-kit0@0.23.3-2

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.

Remediation

Upgrade p11-kit to version or higher.

References

high severity

Buffer Overflow

  • Vulnerable module: perl
  • Introduced through: perl@5.24.1-3+deb9u5, perl/libperl5.24@5.24.1-3+deb9u5 and others
  • Fixed in: 5.24.1-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-modules-5.24@5.24.1-3+deb9u5

Overview

Affected versions of this package are vulnerable to Buffer Overflow regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

Remediation

Upgrade perl to version or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: perl
  • Introduced through: perl@5.24.1-3+deb9u5, perl/libperl5.24@5.24.1-3+deb9u5 and others
  • Fixed in: 5.24.1-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-modules-5.24@5.24.1-3+deb9u5

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

Remediation

Upgrade perl to version or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: perl
  • Introduced through: perl@5.24.1-3+deb9u5, perl/libperl5.24@5.24.1-3+deb9u5 and others
  • Fixed in: 5.24.1-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* perl/perl-modules-5.24@5.24.1-3+deb9u5

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

Remediation

Upgrade perl to version or higher.

References

high severity

Insufficient Comparison

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.20-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

Affected versions of this package are vulnerable to Insufficient Comparison. A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code as the operating system account running psql. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade postgresql-9.6 to version or higher.

References

high severity

SQL Injection

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.20-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

Affected versions of this package are vulnerable to SQL Injection. A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade postgresql-9.6 to version or higher.

References

high severity

SQL Injection

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.15-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

A flaw was discovered in postgresql versions 9.4.x before 9.4.24, 9.5.x before 9.5.19, 9.6.x before 9.6.15, 10.x before 10.10 and 11.x before 11.5 where arbitrary SQL statements can be executed given a suitable SECURITY DEFINER function. An attacker, with EXECUTE permission on the function, can execute arbitrary SQL as the owner of the function.

References

high severity

Untrusted Search Path

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.19-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

Affected versions of this package are vulnerable to Untrusted Search Path. It was found that some PostgreSQL extensions did not use search_path safely in their installation script. An attacker with sufficient privileges could use this flaw to trick an administrator into executing a specially crafted script, during the installation or update of such extension. This affects PostgreSQL versions before 12.4, before 11.9, before 10.14, before 9.6.19, and before 9.5.23.

Remediation

Upgrade postgresql-9.6 to version or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.20-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm. A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade postgresql-9.6 to version or higher.

References

high severity

Directory Traversal

  • Vulnerable module: python-pip
  • Introduced through: python-pip@9.0.1-2 and python-pip/python-pip-whl@9.0.1-2
  • Fixed in: 9.0.1-2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python-pip@9.0.1-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python-pip/python-pip-whl@9.0.1-2

Overview

Affected versions of this package are vulnerable to Directory Traversal. The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py.

Remediation

Upgrade python-pip to version or higher.

References

high severity

Security Features

  • Vulnerable module: python-virtualenv
  • Introduced through: python-virtualenv@15.1.0+ds-1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python-virtualenv@15.1.0+ds-1

Overview

** DISPUTED ** Virtualenv 16.0.0 allows a sandbox escape via "python $(bash >&2)" and "python $(rbash >&2)" commands. NOTE: the software maintainer disputes this because the Python interpreter in a virtualenv is supposed to be able to execute arbitrary code.

References

high severity

Credentials Management

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

Python 2.7.x through 2.7.16 and 3.x through 3.7.2 is affected by: Improper Handling of Unicode Encoding (with an incorrect netloc) during NFKC normalization. The impact is: Information disclosure (credentials, cookies, etc. that are cached against a given hostname). The components are: urllib.parse.urlsplit, urllib.parse.urlparse. The attack vector is: A specially crafted URL could be incorrectly parsed to locate cookies or authentication data and send that information to a different host than when parsed correctly. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.7, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.3, v3.7.3rc1, v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.

References

high severity

Directory Traversal

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call.

References

high severity

Improper Input Validation

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

An issue was discovered in Python through 2.7.16, 3.x through 3.5.7, 3.6.x through 3.6.9, and 3.7.x through 3.7.4. The email module wrongly parses email addresses that contain multiple @ characters. An application that uses the email module and implements some kind of checks on the From/To headers of a message could be tricked into accepting an email address that should be denied. An attack may be the same as in CVE-2019-11340; however, this CVE applies to Python more generally.

References

high severity

Improper Input Validation

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

Affected versions of this package are vulnerable to Improper Input Validation. In Lib/tarfile.py in Python through 3.8.3, an attacker is able to craft a TAR archive leading to an infinite loop when opened by tarfile.open, because _proc_pax lacks header validation.

Remediation

Upgrade python2.7 to version or higher.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

An exploitable denial-of-service vulnerability exists in the X509 certificate parser of Python.org Python 2.7.11 / 3.6.6. A specially crafted X509 certificate can cause a NULL pointer dereference, resulting in a denial of service. An attacker can initiate or accept TLS connections using crafted certificates to trigger this vulnerability.

References

high severity

Out-of-Bounds

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.4-4.1 and shadow/passwd@1:4.4-4.1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* shadow/passwd@1:4.4-4.1

Overview

In shadow before 4.5, the newusers tool could be made to manipulate internal data structures in ways unintended by the authors. Malformed input may lead to crashes (with a buffer overflow or other memory corruption) or other unspecified behaviors. This crosses a privilege boundary in, for example, certain web-hosting environments in which a Control Panel allows an unprivileged user account to create subaccounts.

References

high severity

Improper Handling of Exceptional Conditions

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.

References

high severity

Improper Input Validation

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries that occur after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases), aka Magellan.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries in a "merge" operation that occurs after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases). This is a different vulnerability than CVE-2018-20346.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

In SQLite through 3.22.0, databases whose schema is corrupted using a CREATE TABLE AS statement could cause a NULL pointer dereference, related to build.c and prepare.c.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

In SQLite 3.27.2, interleaving reads and writes in a single transaction with an fts5 virtual table will lead to a NULL Pointer Dereference in fts5ChunkIterate in sqlite3.c. This is related to ext/fts5/fts5_hash.c and ext/fts5/fts5_index.c.

References

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

In SQLite 3.27.2, running fts5 prefix queries inside a transaction could trigger a heap-based buffer over-read in fts5HashEntrySort in sqlite3.c, which may lead to an information leak. This is related to ext/fts5/fts5_hash.c.

References

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. An out-of-bounds read was addressed with improved bounds checking. This issue is fixed in iOS 13.5 and iPadOS 13.5, macOS Catalina 10.15.5, tvOS 13.4.5, watchOS 6.2.5, iTunes 12.10.7 for Windows, iCloud for Windows 11.2, iCloud for Windows 7.19. A malicious application may cause a denial of service or potentially disclose memory contents.

Remediation

There is no fixed version for sqlite3.

References

high severity

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Integer overflow in SQLite via WebSQL in Google Chrome prior to 74.0.3729.131 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

References

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Affected versions of this package are vulnerable to Use After Free ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Remediation

Upgrade sqlite3 to version or higher.

References

high severity

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Affected versions of this package are vulnerable to Use After Free. SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.

Remediation

Upgrade sqlite3 to version or higher.

References

high severity

Access Restriction Bypass

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9
  • Fixed in: 232-25+deb9u11

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the "allow_active" element rather than "allow_any".

References

high severity

Deserialization of Untrusted Data

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9
  • Fixed in: 232-25+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

A vulnerability in unit_deserialize of systemd allows an attacker to supply arbitrary state across systemd re-execution via NotifyAccess. This can be used to improperly influence systemd execution and possibly lead to root privilege escalation. Affected releases are systemd versions up to and including 239.

References

high severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.

References

high severity

Information Exposure

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

systemd 242 changes the VT1 mode upon a logout, which allows attackers to read cleartext passwords in certain circumstances, such as watching a shutdown, or using Ctrl-Alt-F1 and Ctrl-Alt-F2. This occurs because the KDGKBMODE (aka current keyboard mode) check is mishandled.

References

high severity

Privilege Chaining

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

References

high severity

Use After Free

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sending specially crafted dbus messages.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

An issue was discovered in LibTIFF 4.0.9. There is a int32 overflow in multiply_ms in tools/ppm2tiff.c, which can cause a denial of service (crash) or possibly have unspecified other impact via a crafted image file.

References

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6 and 4.0.9 allows remote attackers to cause a denial of service (crash) or possibly have unspecified other impact via a crafted TIFF file.

References

high severity

Out-of-bounds Write

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer overflow via a crafted RGBA image, related to a "Negative-size-param" condition.

References

high severity

Access Restriction Bypass

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.29.2-1+deb9u1, util-linux/bsdutils@1:2.29.2-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/bsdutils@1:2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/libblkid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/libfdisk1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/libmount1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/libsmartcols1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/libuuid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* util-linux/mount@2.29.2-1+deb9u1

Overview

runuser in util-linux allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

References

medium severity

Improper Input Validation

  • Vulnerable module: apt
  • Introduced through: apt@1.4.9, apt/apt-transport-https@1.4.9 and others
  • Fixed in: 1.4.10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/libapt-pkg5.0@1.4.9

Overview

Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: apt
  • Introduced through: apt@1.4.9, apt/apt-transport-https@1.4.9 and others
  • Fixed in: 1.4.11

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/libapt-pkg5.0@1.4.9

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. APT had several integer overflows and underflows while parsing .deb packages, aka GHSL-2020-168 GHSL-2020-169, in files apt-pkg/contrib/extracttar.cc, apt-pkg/deb/debfile.cc, and apt-pkg/contrib/arfile.cc. This issue affects: apt 1.2.32ubuntu0 versions prior to 1.2.32ubuntu0.2; 1.6.12ubuntu0 versions prior to 1.6.12ubuntu0.2; 2.0.2ubuntu0 versions prior to 2.0.2ubuntu0.2; 2.1.10ubuntu0 versions prior to 2.1.10ubuntu0.1;

Remediation

Upgrade apt to version or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is an attempted excessive memory allocation in setup_group in elf.c.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is an attempted excessive memory allocation in elf_read_notes in elf.c.

References

medium severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The aout_32_swap_std_reloc_out function in aoutx.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils before 2.31, allows remote attackers to cause a denial of service (segmentation fault and application crash) via a crafted file, as demonstrated by objcopy.

References

medium severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The bfd_get_debug_link_info_1 function in opncls.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, has an unchecked strnlen operation. Remote attackers could leverage this vulnerability to cause a denial of service (segmentation fault) via a crafted ELF file.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The parse_die function in dwarf1.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (integer overflow and application crash) via an ELF file with corrupt dwarf1 debug information, as demonstrated by nm.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (integer underflow or overflow, and application crash) via an ELF file with a corrupt DWARF FORM block, as demonstrated by nm.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The assign_file_positions_for_non_load_sections function in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an ELF file with a RELRO segment that lacks a matching LOAD segment, as demonstrated by objcopy.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The ignore_section_sym function in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, does not validate the output_section pointer in the case of a symtab entry with a "SECTION" type that has a "0" value, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file, as demonstrated by objcopy.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The swap_std_reloc_in function in aoutx.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (aout_32_swap_std_reloc_out NULL pointer dereference and application crash) via a crafted ELF file, as demonstrated by objcopy.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

concat_filename in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted binary file, as demonstrated by nm-new.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The *_get_synthetic_symtab functions in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, mishandle the failure of a certain canonicalization step, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file, related to elf32-i386.c and elf64-x86-64.c.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The getsym function in tekhex.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (stack-based buffer over-read and application crash) via a malformed tekhex binary.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The get_build_id function in opncls.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted file in which a certain size field is larger than a corresponding data field, as demonstrated by mishandling within the objdump program.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

process_cu_tu_index in dwarf.c in GNU Binutils 2.30 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted binary file, as demonstrated by readelf.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The pe_print_idata function in peXXigen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, mishandles HintName vector entries, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted PE file, related to the bfd_getl16 function.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The getvalue function in tekhex.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, allows remote attackers to cause a denial of service (stack-based buffer over-read and application crash) via a crafted tekhex file, as demonstrated by mishandling within the nm program.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The elf_parse_notes function in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (out-of-bounds read and segmentation violation) via a note with a large alignment.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, does not validate the PLT section size, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file, related to elf_i386_get_synthetic_symtab in elf32-i386.c and elf_x86_64_get_synthetic_symtab in elf64-x86-64.c.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The _bfd_XX_bfd_copy_private_bfd_data_common function in peXXigen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, processes a negative Data Directory size with an unbounded loop that increases the value of (external_IMAGE_DEBUG_DIRECTORY) *edd so that the address exceeds its own memory region, resulting in an out-of-bounds memory write, as demonstrated by objcopy copying private info with _bfd_pex64_bfd_copy_private_bfd_data_common in pex64igen.c.

References

medium severity

Resource Exhaustion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

An issue was discovered in arm_pt in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_arm_hp_template, demangle_class_name, demangle_fund_type, do_type, do_arg, demangle_args, and demangle_nested_args. This can occur during execution of nm-new.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.43.4-2, e2fsprogs/e2fslibs@1.43.4-2 and others
  • Fixed in: 1.43.4-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/e2fslibs@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/libcomerr2@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/libss2@1.43.4-2

Overview

An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.43.4-2, e2fsprogs/e2fslibs@1.43.4-2 and others
  • Fixed in: 1.43.4-2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/e2fslibs@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/libcomerr2@1.43.4-2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* e2fsprogs/libss2@1.43.4-2

Overview

A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.6.3-3.2
  • Fixed in: 2.6.3-3.2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* freetype/libfreetype6@2.6.3-3.2

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade freetype to version or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

The DNS stub resolver in the GNU C Library (aka glibc or libc6) before version 2.26, when EDNS support is enabled, will solicit large UDP responses from name servers, potentially simplifying off-path DNS spoofing attacks due to IP fragmentation.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possibility of embedded HTTP headers or other potentially dangerous substrings.

References

medium severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long double function contains a non-canonical bit pattern, a seen when passing a 0x5d414141414141410000 value to sinl on x86 targets. This is related to sysdeps/ieee754/ldbl-96/e_rem_pio2l.c.

References

medium severity

new

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* glibc/multiarch-support@2.24-11+deb9u4

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

There is no fixed version for glibc.

References

medium severity

Information Exposure

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.8-5+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* gnutls28/libgnutls30@3.5.8-5+deb9u4

Overview

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.15-1+deb9u1, krb5/libk5crypto3@1.15-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5support0@1.15-1+deb9u1

Overview

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. The pre-defined function "strlen" is getting a "NULL" string as a parameter value in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in the Key Distribution Center (KDC), which allows remote authenticated users to cause a denial of service (NULL pointer dereference) via a modified kadmin client.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.15-1+deb9u1, krb5/libk5crypto3@1.15-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* krb5/libkrb5support0@1.15-1+deb9u1

Overview

MIT krb5 1.6 or later allows an authenticated kadmin with permission to add principals to an LDAP Kerberos database to cause a denial of service (NULL pointer dereference) or bypass a DN container check by supplying tagged data that is internal to the database module.

References

medium severity

Cryptographic Issues

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.7.6-2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libgcrypt20@1.7.6-2+deb9u3

Overview

In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.)

References

medium severity

Race Condition

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.7.6-2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libgcrypt20@1.7.6-2+deb9u3

Overview

It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.2.4-2+deb9u4
  • Fixed in: 2.2.4-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libgd2/libgd3@2.2.4-2+deb9u4

Overview

When using the gdImageCreateFromXbm() function in the GD Graphics Library (aka LibGD) 2.2.5, as used in the PHP GD extension in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6, it is possible to supply data that will cause the function to use the value of uninitialized variable. This may lead to disclosing contents of the stack that has been left there by previous code.

References

medium severity

Divide By Zero

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2
  • Fixed in: 1:1.5.1-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Overview

libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2
  • Fixed in: 1:1.5.1-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Overview

get_8bit_row in rdbmp.c in libjpeg-turbo through 1.5.90 and MozJPEG through 3.3.1 allows attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted 8-bit BMP in which one or more of the color indices is out of range for the number of palette entries.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.28-1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libpng1.6/libpng16-16@1.6.28-1

Overview

gif2png 2.5.13 has a memory leak in the writefile function.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.6.4-3+deb9u1 and libx11/libx11-data@2:1.6.4-3+deb9u1
  • Fixed in: 2:1.6.4-3+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libx11/libx11-6@2:1.6.4-3+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libx11/libx11-data@2:1.6.4-3+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. An integer overflow leading to a heap-buffer overflow was found in The X Input Method (XIM) client was implemented in libX11 before version 1.6.10. As per upstream this is security relevant when setuid programs call XIM client functions while running with elevated privileges. No such programs are shipped with Red Hat Enterprise Linux.

Remediation

Upgrade libx11 to version or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

** DISPUTED ** libxml2 2.9.4, when used in recover mode, allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted XML document. NOTE: The maintainer states "I would disagree of a CVE with the Recover parsing option which should only be used for manual recovery at least for XML parser."

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2
  • Fixed in: 2.9.4+dfsg1-2.2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

Remediation

Upgrade libxml2 to version or higher.

References

medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.4+dfsg1-2.2+deb9u2 and libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

Overview

libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the current document may be read but other files may not be opened, which makes it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document.

References

medium severity

Information Exposure

  • Vulnerable module: nettle/libhogweed4
  • Introduced through: nettle/libhogweed4@3.3-1+b2 and nettle/libnettle6@3.3-1+b2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nettle/libhogweed4@3.3-1+b2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nettle/libnettle6@3.3-1+b2

Overview

A Bleichenbacher type side-channel based padding oracle attack was found in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run a process on the same physical core as the victim process, could use this flaw extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

References

medium severity

HTTP Request Smuggling

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others
  • Fixed in: 1.10.3-1+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* nginx/nginx-full@1.10.3-1+deb9u2

Overview

NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer.

References

medium severity

Buffer Overflow

  • Vulnerable module: node
  • Introduced through: node@8.12.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Buffer Overflow. realpath() implementation performs an incorrect calculation when allocating a buffer, leading to a potential buffer overflow.

Remediation

Upgrade node to version 10.22.1, 12.18.4, 14.9.0 or higher.

References

medium severity

Hostname Spoofing

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Hostname Spoofing. If a Node.js application is using url.parse() to determine the URL hostname, that hostname can be spoofed by using a mixed case "javascript:" (e.g. "javAscript:") protocol (other protocols are not affected). If security decisions are made about the URL based on the hostname, they may be incorrect.

Remediation

Upgrade node to version 6.15.0, 8.14.0, 10.14.0, 11.3.0 or higher.

References

medium severity

HTTP request splitting

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to HTTP request splitting. If Node.js can be convinced to use unsanitized user-provided Unicode data for the path option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the same server.

Remediation

Upgrade node to version 6.15.0, 8.14.0 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.15.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Information Exposure. Under certain circumstances, a TLS server can be forced to respond differently to a client if a zero-byte record is received with an invalid padding compared to a zero-byte record with an invalid MAC. This can be used as the basis of a padding oracle attack to decrypt data.

Only TLS connections using certain ciphersuites executing under certain conditions are exploitable. Node are currently unable to determine whether the use of OpenSSL in Node.js exposes this vulnerability. They are taking a cautionary approach and recommending the same for users.

Remediation

Upgrade node to version 6.17.0, 8.15.1 or higher.

References

medium severity

new

Use After Free

  • Vulnerable module: node
  • Introduced through: node@8.12.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.4.4-20190405T092712Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Use After Free. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult structure. This may be exploited to corrupt memory.

Remediation

Upgrade node to version 10.23.1, 12.20.1, 14.15.4, 15.5.1 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2
  • Fixed in: 2.4.44+dfsg-5+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Overview

An issue was discovered in the server in OpenLDAP before 2.4.48. When the server administrator delegates rootDN (database admin) privileges for certain databases but wants to maintain isolation (e.g., for multi-tenant deployments), slapd does not properly stop a rootDN from requesting authorization as an identity from another database during a SASL bind or with a proxyAuthz (RFC 4370) control. (It is not a common configuration to deploy a system where the server administrator and a DB administrator enjoy different levels of trust.)

References

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others
  • Fixed in: 1.1.0l-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl1.1@1.1.0j-1~deb9u1

Overview

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others
  • Fixed in: 1.1.0l-1~deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl/libssl1.1@1.1.0j-1~deb9u1

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

Remediation

Upgrade openssl to version or higher.

References

medium severity

Information Exposure

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1
  • Fixed in: 1.0.2u-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

Overview

There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

References

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1
  • Fixed in: 1.0.2t-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

Overview

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1
  • Fixed in: 1.0.2u-1~deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

Remediation

Upgrade openssl1.0 to version or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.23.3-2
  • Fixed in: 0.23.3-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* p11-kit/libp11-kit0@0.23.3-2

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.

Remediation

Upgrade p11-kit to version or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre3/libpcre16-3
  • Introduced through: pcre3/libpcre16-3@2:8.39-3, pcre3/libpcre3@2:8.39-3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* pcre3/libpcrecpp0v5@2:8.39-3

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.

Remediation

There is no fixed version for pcre3.

References

medium severity

Improper Access Control

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.13-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

A vulnerability was found in PostgreSQL versions 11.x up to excluding 11.3, 10.x up to excluding 10.8, 9.6.x up to, excluding 9.6.13, 9.5.x up to, excluding 9.5.17. PostgreSQL maintains column statistics for tables. Certain statistics, such as histograms and lists of most common values, contain values taken from the column. PostgreSQL does not evaluate row security policies before consulting those statistics during query planning; an attacker can exploit this to read the most common values of certain columns. Affected columns are those for which the attacker has SELECT privilege and for which, in an ordinary query, row-level security prunes the set of rows visible to the attacker.

References

medium severity

Missing Authorization

  • Vulnerable module: postgresql-9.6/libpq-dev
  • Introduced through: postgresql-9.6/libpq-dev@9.6.11-0+deb9u1 and postgresql-9.6/libpq5@9.6.11-0+deb9u1
  • Fixed in: 9.6.17-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* postgresql-9.6/libpq5@9.6.11-0+deb9u1

Overview

A flaw was found in PostgreSQL's "ALTER ... DEPENDS ON EXTENSION", where sub-commands did not perform authorization checks. An authenticated attacker could use this flaw in certain configurations to perform drop objects such as function, triggers, et al., leading to database corruption. This issue affects PostgreSQL versions before 12.2, before 11.7, before 10.12 and before 9.6.17.

References

medium severity

CRLF Injection

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string after a ? character) followed by an HTTP header or a Redis command. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.

References

medium severity

CRLF Injection

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.

References

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

The documentation XML-RPC server in Python through 2.7.16, 3.x through 3.6.9, and 3.7.x through 3.7.4 has XSS via the server_title field. This occurs in Lib/DocXMLRPCServer.py in Python 2.x, and in Lib/xmlrpc/server.py in Python 3.x. If set_server_title is called with untrusted input, arbitrary JavaScript can be delivered to clients that visit the http URL for this server.

References

medium severity

Improper Input Validation

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* python2.7/python2.7-minimal@2.7.13-2+deb9u3

Overview

http.cookiejar.DefaultPolicy.domain_return_ok in Lib/http/cookiejar.py in Python before 3.7.3 does not correctly validate the domain: it can be tricked into sending existing cookies to the wrong server. An attacker may abuse this flaw by using a server with a hostname that has another valid hostname as a suffix (e.g., pythonicexample.com to steal cookies for example.com). When a program uses http.cookiejar.DefaultPolicy and tries to do an HTTP connection to an attacker-controlled server, existing cookies can be leaked to the attacker. This affects 2.x through 2.7.16, 3.x before 3.4.10, 3.5.x before 3.5.7, 3.6.x before 3.6.9, and 3.7.x before 3.7.3.

References

medium severity

Divide By Zero

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade sqlite3 to version or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1
  • Fixed in: 3.16.2-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.

Remediation

Upgrade sqlite3 to version or higher.

References

medium severity

Race Condition

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9
  • Fixed in: 232-25+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* systemd/libudev1@232-25+deb9u9

Overview

In systemd prior to 234 a race condition exists between .mount and .automount units such that automount requests from kernel may not be serviced by systemd resulting in kernel holding the mountpoint and any processes that try to use said mount will hang. A race condition like this may lead to denial of service, until mount points are unmounted.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-1.1

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tar@1.29b-1.1

Overview

GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root).

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

_TIFFCheckMalloc and _TIFFCheckRealloc in tif_aux.c in LibTIFF through 4.0.10 mishandle Integer Overflow checks because they rely on compiler behavior that is undefined by the applicable C standards. This can, for example, lead to an application crash.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that will lead to a denial of service attack, as demonstrated by tiffset.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

A NULL pointer dereference in the function _TIFFmemcmp at tif_unix.c (called from TIFFWriteDirectoryTagTransferfunction) in LibTIFF 4.0.9 allows an attacker to cause a denial-of-service through a crafted tiff file. This vulnerability can be triggered by the executable tiffcp.

References

medium severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4
  • Fixed in: 4.0.8-2+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* tiff/libtiff5@4.0.8-2+deb9u4

Overview

An Invalid Address dereference was discovered in TIFFWriteDirectoryTagTransferfunction in libtiff/tif_dirwrite.c in LibTIFF 4.0.10, affecting the cpSeparateBufToContigBuf function in tiffcp.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted tiff file. This is different from CVE-2018-12900.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.4.9, apt/apt-transport-https@1.4.9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* apt/libapt-pkg5.0@1.4.9

Overview

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

References

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@4.4-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* bash@4.4-5

Overview

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is an attempted excessive memory allocation in _bfd_elf_slurp_version_tables in elf.c.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

GNU Binutils 2.28 allows remote attackers to cause a denial of service (memory consumption) via a crafted ELF file with many program headers, related to the get_program_headers function in readelf.c.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted ELF file, as demonstrated by _bfd_elf_parse_attributes in elf-attrs.c and bfd_malloc in libbfd.c. This can occur during execution of nm.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

_bfd_elf_slurp_version_tables in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted ELF file.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

remember_Ktype in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30, allows attackers to trigger excessive memory consumption (aka OOM). This can occur during execution of cxxfilt.

References

low severity

Divide By Zero

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

decode_line_info in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted ELF file.

References

low severity

Double Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

Affected versions of this package are vulnerable to Double Free. A double free vulnerability exists in the Binary File Descriptor (BFD) (aka libbrd) in GNU Binutils 2.34 in the process_symbol_table, as demonstrated in readelf, via a crafted file.

Remediation

There is no fixed version for binutils.

References

low severity

new

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

Affected versions of this package are vulnerable to Improper Input Validation. A flaw exists in binutils in bfd/pef.c. An attacker who is able to submit a crafted PEF file to be parsed by objdump could cause a heap buffer overflow -> out-of-bounds read that could lead to an impact to application availability. This flaw affects binutils versions prior to 2.34.

Remediation

There is no fixed version for binutils.

References

low severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

readelf.c in GNU Binutils 2017-04-12 has a "shift exponent too large for type unsigned long" issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted ELF file.

References

low severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The bfd_section_from_shdr function in elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers to cause a denial of service (segmentation fault) via a large attribute section.

References

low severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

GNU binutils gold gold v1.11-v1.16 (GNU binutils v2.21-v2.31.1) is affected by: Improper Input Validation, Signed/Unsigned Comparison, Out-of-bounds Read. The impact is: Denial of service. The component is: gold/fileread.cc:497, elfcpp/elfcpp_file.h:644. The attack vector is: An ELF file with an invalid e_shoff header field must be opened.

References

low severity

Incorrect Calculation of Buffer Size

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

process_debug_info in dwarf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (infinite loop) via a crafted ELF file that contains a negative size value in a CU structure.

References

low severity

Incorrect Type Conversion or Cast

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

readelf.c in GNU Binutils 2017-04-12 has a "cannot be represented in type long" issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted ELF file.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

The print_gnu_property_note function in readelf.c in GNU Binutils 2.29.1 does not have integer-overflow protection on 32-bit platforms, which allows remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted ELF file.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base:4.4.4-20190405T092712Z@* binutils@2.28-5

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils through 2.31. There is an integer overflow and infinite loop caused by the IS_CONTAINED_BY_LMA macro in elf.c.

References

low severity