Docker digitalmarketplace/base:3.1.0

Vulnerabilities

559 via 1227 paths

Dependencies

212

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
  • 222
  • 106
  • 231
Status
  • 559
  • 0
  • 0
OS binaries
  • 545
  • 14

high severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* apt@1.4.8
  • Introduced through: digitalmarketplace/base:3.1.0@* apt/apt-transport-https@1.4.8
  • Introduced through: digitalmarketplace/base:3.1.0@* apt/libapt-pkg5.0@1.4.8

Overview

Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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+deb9u4, curl/libcurl3@7.52.1-5+deb9u4 and others
  • Fixed in: 7.52.1-5+deb9u11

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

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+deb9u4, curl/libcurl3@7.52.1-5+deb9u4 and others
  • Fixed in: 7.52.1-5+deb9u10

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

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

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

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+deb9u4, curl/libcurl3@7.52.1-5+deb9u4 and others
  • Fixed in: 7.52.1-5+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

Overview

libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

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

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* curl@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3@7.52.1-5+deb9u4
  • Introduced through: digitalmarketplace/base:3.1.0@* curl/libcurl3-gnutls@7.52.1-5+deb9u4

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:3.1.0@* cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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, gcc-6/cpp-6@6.3.0-18 and others

Detailed paths

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

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

Arbitrary Argument Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

Overview

Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.

References

high severity

CVE-2019-1353

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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

Directory Traversal

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

Overview

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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+deb9u2 and git/git-man@1:2.11.0-3+deb9u2
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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+deb9u2 and git/git-man@1:2.11.0-3+deb9u2
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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+deb9u2 and git/git-man@1:2.11.0-3+deb9u2
  • Fixed in: 1:2.11.0-3+deb9u6

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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+deb9u2 and git/git-man@1:2.11.0-3+deb9u2
  • Fixed in: 1:2.11.0-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

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

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* git@1:2.11.0-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* git/git-man@1:2.11.0-3+deb9u2

Overview

In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory.

References

high severity

Improper Data Handling

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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

Missing Release of Resource after Effective Lifetime

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

A memory leak in glibc 2.1.1 (released on May 24, 1999) can be reached and amplified through the LD_HWCAP_MASK environment variable. Please note that many versions of glibc are not vulnerable to this issue if patched for CVE-2017-1000366.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

The glob function in glob.c in the GNU C Library (aka glibc or libc6) before 2.27 contains a buffer overflow during unescaping of user names with the ~ operator.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

A buffer overflow in glibc 2.5 (released on September 29, 2006) and can be triggered through the LD_LIBRARY_PATH environment variable. Please note that many versions of glibc are not vulnerable to this issue if patched for CVE-2017-1000366.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

The GNU C Library (aka glibc or libc6) before 2.27 contains an off-by-one error leading to a heap-based buffer overflow in the glob function in glob.c, related to the processing of home directories using the ~ operator followed by a long string.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

An SSE2-optimized memmove implementation for i386 in sysdeps/i386/i686/multiarch/memcpy-sse2-unaligned.S in the GNU C Library (aka glibc or libc6) 2.21 through 2.27 does not correctly perform the overlapping memory check if the source memory range spans the middle of the address space, resulting in corrupt data being produced by the copy operation. This may disclose information to context-dependent attackers, or result in a denial of service, or, possibly, code execution.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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+deb9u1, glibc/libc-dev-bin@2.24-11+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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+deb9u1, glibc/libc-dev-bin@2.24-11+deb9u1 and others
  • Fixed in: 2.24-11+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

stdlib/canonicalize.c in the GNU C Library (aka glibc or libc6) 2.27 and earlier, when processing very long pathname arguments to the realpath function, could encounter an integer overflow on 32-bit architectures, leading to a stack-based buffer overflow and, potentially, arbitrary code execution.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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+deb9u1, glibc/libc-dev-bin@2.24-11+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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+deb9u1, glibc/libc-dev-bin@2.24-11+deb9u1 and others
  • Fixed in: 2.24-11+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

An AVX-512-optimized implementation of the mempcpy function in the GNU C Library (aka glibc or libc6) 2.27 and earlier may write data beyond the target buffer, leading to a buffer overflow in __mempcpy_avx512_no_vzeroupper.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

Affected versions of this package are vulnerable to Reachable Assertion. The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid input sequences in the ISO-2022-JP-3 encoding, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

There is no fixed version for glibc.

References

high severity

Untrusted Search Path

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

Overview

elf/dl-load.c in the GNU C Library (aka glibc or libc6) 2.19 through 2.26 mishandles RPATH and RUNPATH containing $ORIGIN for a privileged (setuid or AT_SECURE) program, which allows local users to gain privileges via a Trojan horse library in the current working directory, related to the fillin_rpath and decompose_rpath functions. This is associated with misinterpretion of an empty RPATH/RUNPATH token as the "./" directory. NOTE: this configuration of RPATH/RUNPATH for a privileged program is apparently very uncommon; most likely, no such program is shipped with any common Linux distribution.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc-dev-bin@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/libc6-dev@2.24-11+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* glibc/multiarch-support@2.24-11+deb9u1

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~deb9u1, gnupg2/gnupg-agent@2.1.18-8~deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gnupg@2.1.18-8~deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gnupg-agent@2.1.18-8~deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gpgv@2.1.18-8~deb9u1

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

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: gnupg2/gnupg
  • Introduced through: gnupg2/gnupg@2.1.18-8~deb9u1, gnupg2/gnupg-agent@2.1.18-8~deb9u1 and others
  • Fixed in: 2.1.18-8~deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gnupg@2.1.18-8~deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gnupg-agent@2.1.18-8~deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* gnupg2/gpgv@2.1.18-8~deb9u1

Overview

mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers to spoof the output that GnuPG sends on file descriptor 2 to other programs that use the "--status-fd 2" option. For example, the OpenPGP data might represent an original filename that contains line feed characters in conjunction with GOODSIG or VALIDSIG status codes.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* gnutls28/libgnutls30@3.5.8-5+deb9u3

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+deb9u1, icu/libicu-dev@57.1-6+deb9u1 and others
  • Fixed in: 57.1-6+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* icu/icu-devtools@57.1-6+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* icu/libicu-dev@57.1-6+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* icu/libicu57@57.1-6+deb9u1

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:3.1.0@* krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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
  • Fixed in: 0.8.3-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* 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

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

Overview

The GD Graphics Library (aka LibGD) 2.2.5 has a double free in the gdImage*Ptr() functions in gd_gif_out.c, gd_jpeg.c, and gd_wbmp.c. NOTE: PHP is unaffected.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

Overview

Libgd version 2.2.5 contains a Double Free Vulnerability vulnerability in gdImageBmpPtr Function that can result in Remote Code Execution . This attack appear to be exploitable via Specially Crafted Jpeg Image can trigger double free. This vulnerability appears to have been fixed in after commit ac16bdf2d41724b5a65255d4c28fb0ec46bc42f5.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

Overview

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-6978. Reason: This candidate is a reservation duplicate of CVE-2019-6978. Notes: All CVE users should reference CVE-2019-6978 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

Overview

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-6978. Reason: This candidate is a reservation duplicate of CVE-2019-6978. Notes: All CVE users should reference CVE-2019-6978 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

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

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libgd2/libgd3@2.2.4-2+deb9u2

Overview

gdImageColorMatch in gd_color_match.c in the GD Graphics Library (aka LibGD) 2.2.5, as used in the imagecolormatch function in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1, has a heap-based buffer overflow. This can be exploited by an attacker who is able to trigger imagecolormatch calls with crafted image data.

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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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

NULL Pointer Dereference

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.10-1.1
  • Fixed in: 4.10-1.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libtasn1-6@4.10-1.1

Overview

The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input that triggers assignment of a NULL value within an asn1_node structure. It may lead to a remote denial of service attack.

References

high severity

Uncontrolled Recursion

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.10-1.1
  • Fixed in: 4.10-1.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libtasn1-6@4.10-1.1

Overview

An issue was discovered in the _asn1_decode_simple_ber function in decoding.c in GNU Libtasn1 before 4.13. Unlimited recursion in the BER decoder leads to stack exhaustion and DoS.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-6@2:1.6.4-3
  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-data@2:1.6.4-3

Overview

An issue was discovered in XListExtensions in ListExt.c in libX11 through 1.6.5. A malicious server can send a reply in which the first string overflows, causing a variable to be set to NULL that will be freed later on, leading to DoS (segmentation fault).

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-6@2:1.6.4-3
  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-data@2:1.6.4-3

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

Off-by-one Error

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-6@2:1.6.4-3
  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-data@2:1.6.4-3

Overview

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c is vulnerable to an off-by-one error caused by malicious server responses, leading to DoS or possibly unspecified other impact.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-6@2:1.6.4-3
  • Introduced through: digitalmarketplace/base:3.1.0@* libx11/libx11-data@2:1.6.4-3

Overview

An issue was discovered in libX11 through 1.6.5. The function XListExtensions in ListExt.c interprets a variable as signed instead of unsigned, resulting in an out-of-bounds write (of up to 128 bytes), leading to DoS or remote code execution.

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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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+deb9u1, ncurses/libtinfo5@6.0+20161126-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/libncursesw5@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/libtinfo5@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/ncurses-base@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/ncurses-bin@6.0+20161126-1+deb9u1

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

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/libncursesw5@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/libtinfo5@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/ncurses-base@6.0+20161126-1+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* ncurses/ncurses-bin@6.0+20161126-1+deb9u1

Overview

Stack-based buffer overflow in the _nc_write_entry function in tinfo/write_entry.c in ncurses 6.0 allows attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted terminfo file, as demonstrated by tic.

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:3.1.0@* 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:3.1.0@* 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+deb9u1, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u1 and others
  • Fixed in: 1.10.3-1+deb9u3

Detailed paths

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

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+deb9u1, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u1 and others
  • Fixed in: 1.10.3-1+deb9u5

Detailed paths

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

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+deb9u1, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u1 and others
  • Fixed in: 1.10.3-1+deb9u2

Detailed paths

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

Overview

nginx before versions 1.15.6 and 1.14.1 has a vulnerability in the implementation of HTTP/2 that can allow for excessive memory consumption. This issue affects nginx compiled with the ngx_http_v2_module (not compiled by default) if the 'http2' option of the 'listen' directive is used in a configuration file.

References

high severity

Resource Exhaustion

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

Detailed paths

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

Overview

nginx before versions 1.15.6 and 1.14.1 has a vulnerability in the implementation of HTTP/2 that can allow for excessive CPU usage. This issue affects nginx compiled with the ngx_http_v2_module (not compiled by default) if the 'http2' option of the 'listen' directive is used in a configuration file.

References

high severity

Resource Exhaustion

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

Detailed paths

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

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

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@6.12.2
  • Fixed in: 6.14.3

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

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). Calling Buffer.fill() or Buffer.alloc() with some parameters could lead to a hang.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade node to version 6.14.3, 8.11.3, 9.11.2 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@6.12.2
  • Fixed in: 6.15.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

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@6.12.2
  • Fixed in: 6.15.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

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

DNS rebinding

  • Vulnerable module: node
  • Introduced through: node@6.12.2
  • Fixed in: 6.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

Overview

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

Affected versions of this package are vulnerable to DNS rebinding. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.

Remediation

Upgrade node to version 6.14.0, 8.11.0, 9.10.0 or higher.

References

high severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

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

Unprotected Primary Channel

  • Vulnerable module: node
  • Introduced through: node@6.12.2
  • Fixed in: 6.15.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@3.1.0 node@6.12.2

Overview

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

Affected versions of this package are vulnerable to Unprotected Primary Channel. Debugger port 5858 listens on any interface by default: When the debugger is enabled with node --debug or node debug, it listens to port 5858 on all interfaces by default. This may allow remote computers to attach to the debug port and evaluate arbitrary JavaScript

Remediation

Upgrade node to version 6.15.0 or higher.

References

high severity

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

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Access of Resource Using Incompatible Type ('Type Confusion'). A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

References

high severity

CVE-2020-36226

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to CVE-2020-36226. A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Double Free. A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade openldap to version 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+deb9u1 and openldap/libldap-common@2.4.44+dfsg-5+deb9u1
  • Fixed in: 2.4.44+dfsg-5+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

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

Integer Underflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Underflow. An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).

Remediation

Upgrade openldap to version or higher.

References

high severity

Integer Underflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Underflow. An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Loop with Unreachable Exit Condition ('Infinite Loop'). A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

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+deb9u1 and openldap/libldap-common@2.4.44+dfsg-5+deb9u1
  • Fixed in: 2.4.44+dfsg-5+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

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

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).

Remediation

Upgrade openldap to version or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Reachable Assertion. A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Reachable Assertion. A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.

Remediation

Upgrade openldap to version or higher.

References

high severity
new

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Reachable Assertion. In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime.

Remediation

Upgrade openldap to version or higher.

References

high severity

Release of Invalid Pointer or Reference

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

Overview

Affected versions of this package are vulnerable to Release of Invalid Pointer or Reference. A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in 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+deb9u1 and openldap/libldap-common@2.4.44+dfsg-5+deb9u1
  • Fixed in: 2.4.44+dfsg-5+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openldap/libldap-common@2.4.44+dfsg-5+deb9u1

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.0f-3+deb9u1, openssl/libssl-dev@1.1.0f-3+deb9u1 and others
  • Fixed in: 1.1.0k-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl-dev@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl1.1@1.1.0f-3+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
new

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl-dev@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl1.1@1.1.0f-3+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl to version or higher.

References

high severity
new

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl-dev@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl1.1@1.1.0f-3+deb9u1

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl to version or higher.

References

high severity

Key Management Errors

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl-dev@1.1.0f-3+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* openssl/libssl1.1@1.1.0f-3+deb9u1

Overview

During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2-1.0.2o).

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2
  • Fixed in: 1.0.2u-1~deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl1.0 to version or higher.

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2
  • Fixed in: 1.0.2u-1~deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).

Remediation

Upgrade openssl1.0 to version or higher.

References

high severity

Key Management Errors

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2
  • Fixed in: 1.0.2q-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* openssl1.0/libssl1.0.2@1.0.2l-2+deb9u2

Overview

During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2-1.0.2o).

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:3.1.0@* 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+deb9u2, perl/libperl5.24@5.24.1-3+deb9u2 and others
  • Fixed in: 5.24.1-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

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+deb9u2, perl/libperl5.24@5.24.1-3+deb9u2 and others
  • Fixed in: 5.24.1-3+deb9u7

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

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

Link Following

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

Overview

In Perl through 5.26.2, the Archive::Tar module allows remote attackers to bypass a directory-traversal protection mechanism, and overwrite arbitrary files, via an archive file containing a symlink and a regular file with the same name.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

Overview

An issue was discovered in Perl 5.22 through 5.26. Matching a crafted locale dependent regular expression can cause a heap-based buffer over-read and potentially information disclosure.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

Overview

Heap-based buffer overflow in the pack function in Perl before 5.26.2 allows context-dependent attackers to execute arbitrary code via a large item count.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

Overview

An issue was discovered in Perl 5.18 through 5.26. A crafted regular expression can cause a heap-based buffer overflow, with control over the bytes written.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* perl@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/libperl5.24@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-base@5.24.1-3+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* perl/perl-modules-5.24@5.24.1-3+deb9u2

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

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-0+deb9u1

Overview

A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database. Versions 9.3 through 10 are affected.

References

high severity

Incorrect Authorization

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-0+deb9u1

Overview

It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table.

References

high severity

Incorrect Permission Assignment for Critical Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-0+deb9u1

Overview

In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of pg_dumpall -g under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.

References

high severity

Incorrect Permission Assignment for Critical Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-0+deb9u1

Overview

postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.

References

high severity

Insufficient Comparison

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-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.6-0+deb9u1 and postgresql-9.6/libpq5@9.6.6-0+deb9u1
  • Fixed in: 9.6.20-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-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.6-0+deb9u1 and postgresql-9.6/libpq5@9.6.6-0+deb9u1
  • Fixed in: 9.6.10-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-0+deb9u1

Overview

A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.

References

high severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-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.6-0+deb9u1 and postgresql-9.6/libpq5@9.6.6-0+deb9u1
  • Fixed in: 9.6.19-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-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.6-0+deb9u1 and postgresql-9.6/libpq5@9.6.6-0+deb9u1
  • Fixed in: 9.6.20-0+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq-dev@9.6.6-0+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* postgresql-9.6/libpq5@9.6.6-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:3.1.0@* python-pip@9.0.1-2
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* 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

Arbitrary Command Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

Overview

Python Software Foundation Python (CPython) version 2.7 contains a CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in shutil module (make_archive function) that can result in Denial of service, Information gain via injection of arbitrary files on the system or entire drive. This attack appear to be exploitable via Passage of unfiltered user input to the function. This vulnerability appears to have been fixed in after commit add531a1e55b0a739b0f42582f1c9747e5649ace.

References

high severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

Overview

Affected versions of this package are vulnerable to Buffer Overflow. Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callproc.c, which may lead to remote code execution in certain Python applications that accept floating-point numbers as untrusted input, as demonstrated by a 1e300 argument to c_double.from_param. This occurs because sprintf is used unsafely.

Remediation

There is no fixed version for python2.7.

References

high severity

Credentials Management

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

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+deb9u2, python2.7/libpython2.7-minimal@2.7.13-2+deb9u2 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

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+deb9u2, python2.7/libpython2.7-minimal@2.7.13-2+deb9u2 and others
  • Fixed in: 2.7.13-2+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

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+deb9u2, python2.7/libpython2.7-minimal@2.7.13-2+deb9u2 and others
  • Fixed in: 2.7.13-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

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

Missing Initialization of Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

Overview

Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization. This could make it easy to conduct denial of service attacks against Expat by constructing an XML document that would cause pathological hash collisions in Expat's internal data structures, consuming large amounts CPU and RAM. The vulnerability exists in Python versions 3.7.0, 3.6.0 through 3.6.6, 3.5.0 through 3.5.6, 3.4.0 through 3.4.9, 2.7.0 through 2.7.15.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-minimal@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/libpython2.7-stdlib@2.7.13-2+deb9u2
  • Introduced through: digitalmarketplace/base:3.1.0@* python2.7/python2.7-minimal@2.7.13-2+deb9u2

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

Arbitrary Code Injection

  • Vulnerable module: sensible-utils
  • Introduced through: sensible-utils@0.0.9
  • Fixed in: 0.0.9+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* sensible-utils@0.0.9

Overview

sensible-browser in sensible-utils before 0.0.11 does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks via a crafted URL, as demonstrated by a --proxy-pac-file argument.

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:3.1.0@* shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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:3.1.0@* 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+deb9u1 and systemd/libudev1@232-25+deb9u1
  • Fixed in: 232-25+deb9u11

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

Overview

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line arguments calls syslog. A local attacker may use this flaw to crash systemd-journald or escalate his privileges. Versions through v240 are vulnerable.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

Overview

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.

References

high severity

Deserialization of Untrusted Data

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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+deb9u1 and systemd/libudev1@232-25+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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+deb9u1 and systemd/libudev1@232-25+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

Overview

In systemd 223 through 235, a remote DNS server can respond with a custom crafted DNS NSEC resource record to trigger an infinite loop in the dns_packet_read_type_window() function of the 'systemd-resolved' service and cause a DoS of the affected service.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

Overview

A buffer overflow vulnerability in the dhcp6 client of systemd allows a malicious dhcp6 server to overwrite heap memory in systemd-networkd. Affected releases are systemd: versions up to and including 239.

References

high severity

Privilege Chaining

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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+deb9u1 and systemd/libudev1@232-25+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libsystemd0@232-25+deb9u1
  • Introduced through: digitalmarketplace/base:3.1.0@* systemd/libudev1@232-25+deb9u1

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

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

The TIFFReadDirEntryArray function in tif_read.c in LibTIFF 4.0.8 mishandles memory allocation for short files, which allows remote attackers to cause a denial of service (allocation failure and application crash) in the TIFFFetchStripThing function in tif_dirread.c during a tiff2pdf invocation.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

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

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

tools/pal2rgb.c in pal2rgb in LibTIFF 4.0.9 allows remote attackers to cause a denial of service (TIFFSetupStrips heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted TIFF file.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

In LibTIFF 4.0.8, there is a heap-based buffer overflow in the t2p_write_pdf function in tools/tiff2pdf.c. This heap overflow could lead to different damages. For example, a crafted TIFF document can lead to an out-of-bounds read in TIFFCleanup, an invalid free in TIFFClose or t2p_free, memory corruption in t2p_readwrite_pdf_image, or a double free in t2p_free. Given these possibilities, it probably could cause arbitrary code execution.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

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+deb9u1
  • Fixed in: 4.0.8-2+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

The function t2p_write_pdf in tiff2pdf.c in LibTIFF 4.0.9 and earlier 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 TIFF file, a similar issue to CVE-2017-9935.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

In LibTIFF 4.0.9, a heap-based buffer overflow occurs in the function LZWDecodeCompat in tif_lzw.c via a crafted TIFF file, as demonstrated by tiff2ps.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

There is a heap based buffer overflow in tools/tiff2pdf.c of LibTIFF 4.0.8 via a PlanarConfig=Contig image, which causes a more than one hundred bytes out-of-bounds write (related to the ZIPDecode function in tif_zip.c). A crafted input may lead to a remote denial of service attack or an arbitrary code execution attack.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

LibTIFF 3.9.3, 3.9.4, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7, 4.0.8 and 4.0.9 (with JBIG enabled) decodes arbitrarily-sized JBIG into a buffer, ignoring the buffer size, which leads to a tif_jbig.c JBIGDecode out-of-bounds write.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

ChopUpSingleUncompressedStrip in tif_dirread.c in LibTIFF 4.0.9 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 TIFF file, as demonstrated by tiff2pdf.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

newoffsets handling in ChopUpSingleUncompressedStrip in tif_dirread.c in LibTIFF 4.0.9 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 TIFF file, as demonstrated by tiff2pdf. This is a different vulnerability than CVE-2018-15209.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:3.1.0@* tiff/libtiff5@4.0.8-2+deb9u1

Overview

An issue was discovered in LibTIFF 4.0.9. There are two out-of-bounds writes in cpTags in tools/tiff2bw.c and tools/pal2rgb.c, which can cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image file.

References