Docker digitalmarketplace/base:1.0

Vulnerabilities

604 via 1238 paths

Dependencies

198

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:8
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 342
  • 251
  • 11
Status
  • 604
  • 0
  • 0
OS binaries
  • 586
  • 18

high severity

Arbitrary Code Injection

  • Vulnerable module: apt
  • Introduced through: apt@1.0.9.8.4 and apt/libapt-pkg4.12@1.0.9.8.4
  • Fixed in: 1.0.9.8.5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* apt@1.0.9.8.4
  • Introduced through: digitalmarketplace/base:1.0@* apt/libapt-pkg4.12@1.0.9.8.4

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 Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@4.3-11+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* bash@4.3-11+deb8u1

Overview

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

References

high severity

Improper Input Validation

  • Vulnerable module: bash
  • Introduced through: bash@4.3-11+deb8u1
  • Fixed in: 4.3-11+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* bash@4.3-11+deb8u1

Overview

rbash in Bash before 4.4-beta2 did not prevent the shell user from modifying BASH_CMDS, thus allowing the user to execute any command with the permissions of the shell.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

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

References

high severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

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

References

high severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, has an aout_link_add_symbols function in bfd/aoutx.h that has an off-by-one vulnerability because it does not carefully check the string offset. The vulnerability could lead to a GNU linker (ld) program crash.

References

high severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid read of size 1 because the existing reloc offset range tests didn't catch small negative offsets less than the size of the reloc field. This vulnerability causes programs that conduct an analysis of binary programs using the libbfd library, such as objdump, to crash.

References

high severity

Improper Input Validation

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The demangler in GNU Libiberty allows remote attackers to cause a denial of service (infinite loop, stack overflow, and crash) via a cycle in the references of remembered mangled types.

References

high severity

Incorrect Type Conversion or Cast

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

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

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

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

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The display_debug_frames function in dwarf.c in GNU Binutils 2.29.1 allows remote attackers to cause a denial of service (integer overflow and heap-based buffer over-read, and application crash) or possibly have unspecified other impact via a crafted ELF file, related to print_debug_frame.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not validate the symbol count, which allows remote attackers to cause a denial of service (integer overflow and application crash, or excessive memory allocation) or possibly have unspecified other impact via a crafted PE file.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The get_count function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31, allows remote attackers to cause a denial of service (malloc called with the result of an integer-overflowing calculation) or possibly have unspecified other impact via a crafted string, as demonstrated by c++filt.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The dump_relocs_in_section function in objdump.c in GNU Binutils 2.29.1 does not check for reloc count integer overflows, which allows remote attackers to cause a denial of service (excessive memory allocation, or heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted PE file.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The pe_bfd_read_buildid function in peicode.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not validate size and offset values in the data dictionary, which allows remote attackers to cause a denial of service (segmentation violation and application crash) or possibly have unspecified other impact via a crafted PE file.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

A Stack Exhaustion issue was discovered in debug_write_type in debug.c in GNU Binutils 2.30 because of DEBUG_KIND_INDIRECT infinite recursion.

References

high severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The find_nearest_line function in addr2line in GNU Binutils 2.28 does not handle the case where the main file name and the directory name are both empty, triggering a NULL pointer dereference and an invalid write, and leading to a program crash.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

elflink.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, has a "member access within null pointer" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via an "int main() {return 0;}" program.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid write of size 8 because of missing a malloc() return-value check to see if memory had actually been allocated in the _bfd_generic_get_section_contents function. This vulnerability causes programs that conduct an analysis of binary programs using the libbfd library, such as objcopy, to crash.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid read of size 4 due to NULL pointer dereferencing of _bfd_elf_large_com_section. This vulnerability causes programs that conduct an analysis of binary programs using the libbfd library, such as objcopy, to crash.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

A NULL pointer dereference (aka SEGV on unknown address 0x000000000000) was discovered in work_stuff_copy_to_from in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. This can occur during execution of objdump.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The score_opcodes function in opcodes/score7-dis.c in GNU Binutils 2.28 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

opcodes/rl78-decode.opc in GNU Binutils 2.28 has an unbounded GETBYTE macro, which 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

Integer overflow in the string_appends function in cplus-dem.c in libiberty allows remote attackers to execute arbitrary code via a crafted executable, which triggers a buffer overflow.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The disassemble_bytes function in objdump.c in GNU Binutils 2.28 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, as demonstrated by mishandling of rae insns printing for this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

bfd/vms-alpha.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file in the _bfd_vms_get_value and _bfd_vms_slurp_etir functions during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The ieee_archive_p function in bfd/ieee.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, might allow remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution. NOTE: this may be related to a compiler bug.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The ieee_object_p function in bfd/ieee.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, might allow remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution. NOTE: this may be related to a compiler bug.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The _bfd_vms_slurp_etir function in bfd/vms-alpha.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

GNU assembler in GNU Binutils 2.28 is vulnerable to a global buffer overflow (of size 1) while attempting to unget an EOF character from the input stream, potentially leading to a program crash.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The aarch64_ext_ldst_reglist function in opcodes/aarch64-dis.c in GNU Binutils 2.28 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

GNU linker (ld) in GNU Binutils 2.28 is vulnerable to a heap-based buffer overflow while processing a bogus input script, leading to a program crash. This relates to lack of '\0' termination of a name field in ldlex.l.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The sh_elf_set_mach_from_flags function in bfd/elf32-sh.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

opcodes/i386-dis.c in GNU Binutils 2.28 does not consider the number of registers for bnd mode, which 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The versados_mkobject function in bfd/versados.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, does not initialize a certain data structure, which 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The process_otr function in bfd/versados.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, does not validate a certain offset, which 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid read of size 1 and an invalid write of size 1 during processing of a corrupt binary containing reloc(s) with negative addresses. This vulnerability causes programs that conduct an analysis of binary programs using the libbfd library, such as objdump, to crash.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The load_debug_section function in readelf.c in GNU Binutils 2.29.1 allows remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via an ELF file that lacks section headers.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The coff_slurp_line_table function in coffcode.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, allows remote attackers to cause a denial of service (invalid memory access and application crash) or possibly have unspecified other impact via a crafted PE file.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

dwarf.c in GNU Binutils 2.28 is vulnerable to an invalid read of size 1 during dumping of debug information from a corrupt binary. This vulnerability causes programs that conduct an analysis of binary programs, such as objdump and readelf, to crash.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The _bfd_coff_read_string_table function in coffgen.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not properly validate the size of the external string table, which allows remote attackers to cause a denial of service (excessive memory consumption, or heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted COFF binary.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, allows remote attackers to cause a denial of service (memory access violation) or possibly have unspecified other impact via a COFF binary in which a relocation refers to a location after the end of the to-be-relocated section.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, miscalculates DW_FORM_ref_addr die refs in the case of a relocatable object file, which allows remote attackers to cause a denial of service (find_abstract_instance_name invalid memory read, segmentation fault, and application crash).

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

elfcomm.c in readelf in GNU Binutils 2.29 allows remote attackers to cause a denial of service (excessive memory allocation) or possibly have unspecified other impact via a crafted ELF file that triggers a "buffer overflow on fuzzed archive header," related to an uninitialized variable, an improper conditional jump, and the get_archive_member_name, process_archive_index_and_symbols, and setup_archive functions.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The regs macros in opcodes/bfin-dis.c in GNU Binutils 2.28 allow remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The print_insn_score32 function in opcodes/score7-dis.c:552 in GNU Binutils 2.28 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, as demonstrated by mishandling of this file during "objdump -D" execution.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The aout_get_external_symbols function in aoutx.h in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, allows remote attackers to cause a denial of service (slurp_symtab invalid free and application crash) or possibly have unspecified other impact via a crafted ELF file.

References

high severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

GNU gdb All versions is affected by: Buffer Overflow - Out of bound memory access. The impact is: Deny of Service, Memory Disclosure, and Possible Code Execution. The component is: The main gdb module. The attack vector is: Open an ELF for debugging. The fixed version is: Not fixed yet.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.32. It is a heap-based buffer over-read in d_expression_1 in cp-demangle.c after many recursive calls.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

readelf in GNU Binutils 2.28 is vulnerable to a heap-based buffer over-read while processing corrupt RL78 binaries. The vulnerability can trigger program crashes. It may lead to an information leak as well.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The pe_ILF_object_p function in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to a heap-based buffer over-read of size 4049 because it uses the strlen function instead of strnlen, leading to program crashes in several utilities such as addr2line, size, and strings. It could lead to information disclosure as well.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid read (of size 8) because of missing a check (in the copy_special_section_fields function) for an invalid sh_link field before attempting to follow it. This vulnerability causes Binutils utilities like strip to crash.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to an invalid read (of size 4) because of missing a check (in the find_link function) for null headers before attempting to match them. This vulnerability causes Binutils utilities like strip to crash.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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 Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, has an aout_link_add_symbols function in bfd/aoutx.h that is vulnerable to a heap-based buffer over-read (off-by-one) because of an incomplete check for invalid string offsets while loading symbols, leading to a GNU linker (ld) program crash.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

dwarf1.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, mishandles pointers, which allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted ELF file, related to parse_die and parse_line_table, as demonstrated by a parse_die heap-based buffer over-read.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, has a swap_std_reloc_out function in bfd/aoutx.h that is vulnerable to an invalid read (of size 4) because of missing checks for relocs that could not be recognised. This vulnerability causes Binutils utilities like strip to crash.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

The Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to a global buffer over-read error because of an assumption made by code that runs for objcopy and strip, that SHT_REL/SHR_RELA sections are always named starting with a .rel/.rela prefix. This vulnerability causes programs that conduct an analysis of binary programs using the libbfd library, such as objcopy and strip, to crash.

References

high severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

nm.c and objdump.c in GNU Binutils 2.29.1 mishandle certain global symbols, which allows remote attackers to cause a denial of service (_bfd_elf_get_symbol_version_string buffer over-read and application crash) or possibly have unspecified other impact via a crafted ELF file.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

An issue was discovered in GNU Binutils 2.32. It is a heap-based buffer overflow in process_mips_specific in readelf.c via a malformed MIPS option section.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is a heap-based buffer overflow in _bfd_archive_64_bit_slurp_armap in archive64.c.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

binutils version 2.32 and earlier contains a Integer Overflow vulnerability in objdump, bfd_get_dynamic_reloc_upper_bound,bfd_canonicalize_dynamic_reloc that can result in Integer overflow trigger heap overflow. Successful exploitation allows execution of arbitrary code.. This attack appear to be exploitable via Local. This vulnerability appears to have been fixed in after commit 3a551c7a1b80fca579461774860574eabfd7f18f.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils through 2.31. There is a heap-based buffer overflow in bfd_elf32_swap_phdr_in in elfcode.h because the number of program headers is not restricted.

References

high severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

finish_stab in stabs.c in GNU Binutils 2.30 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write of 8 bytes. This can occur during execution of objdump.

References

high severity

Resource Management Errors

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

Overview

demangle_template in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30, allows attackers to trigger excessive memory consumption (aka OOM) during the "Create an array for saving the template argument values" XNEWVEC call. This can occur during execution of objdump.

References

high severity

Use After Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.25-5+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* binutils@2.25-5+deb8u1

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-7+b3
  • Fixed in: 1.0.6-7+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* bzip2/libbz2-1.0@1.0.6-7+b3

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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

There is no fixed version for curl.

References

high severity

Buffer Overflow

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u16

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

high severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u13

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

curl and libcurl before 7.50.2, when built with NSS and the libnsspem.so library is available at runtime, allow remote attackers to hijack the authentication of a TLS connection by leveraging reuse of a previously loaded client certificate from file for a connection for which no certificate has been set, a different vulnerability than CVE-2016-5420.

References

high severity

Improper Input Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

curl before version 7.51.0 uses outdated IDNA 2003 standard to handle International Domain Names and this may lead users to potentially and unknowingly issue network transfer requests to the wrong host.

References

high severity

Information Exposure

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u9

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the Location: response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom Authorization: headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u13

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

Multiple integer overflows in the (1) curl_escape, (2) curl_easy_escape, (3) curl_unescape, and (4) curl_easy_unescape functions in libcurl before 7.50.3 allow attackers to have unspecified impact via a string of length 0xffffffff, which triggers a heap-based buffer overflow.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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

Integer Overflow or Wraparound

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u10

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

high severity

Out-of-Bounds

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u7

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invokes strlen() on the data to figure out the length. The strlen() is called on a heap based buffer that might not be zero terminated so libcurl might read beyond the end of it into whatever memory lies after (or just crash) and then deliver that to the application as if it was actually downloaded.

References

high severity

Out-of-Bounds

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u13

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the PWD command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit 415d2e7cb7, March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.

References

high severity

Out-of-Bounds

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u13

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

curl before version 7.52.0 is vulnerable to a buffer overflow when doing a large floating point output in libcurl's implementation of the printf() functions. If there are any application that accepts a format string from the outside without necessary input filtering, it could allow remote attacks.

References

high severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u14

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u14

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u11

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u13

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u10

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

high severity

Out-of-bounds Read

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

Overview

The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.

References

high severity

Out-of-bounds Write

  • Vulnerable module: curl
  • Introduced through: curl@7.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u14

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u15

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

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.38.0-4+deb8u5, curl/libcurl3@7.38.0-4+deb8u5 and others
  • Fixed in: 7.38.0-4+deb8u10

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* curl@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3@7.38.0-4+deb8u5
  • Introduced through: digitalmarketplace/base:1.0@* curl/libcurl3-gnutls@7.38.0-4+deb8u5

high severity

Out-of-bounds Write

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.26.dfsg1-13+deb8u1 and cyrus-sasl2/libsasl2-modules-db@2.1.26.dfsg1-13+deb8u1
  • Fixed in: 2.1.26.dfsg1-13+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* cyrus-sasl2/libsasl2-2@2.1.26.dfsg1-13+deb8u1
  • Introduced through: digitalmarketplace/base:1.0@* cyrus-sasl2/libsasl2-modules-db@2.1.26.dfsg1-13+deb8u1

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

Access Restriction Bypass

  • Vulnerable module: db5.3/libdb5.3
  • Introduced through: db5.3/libdb5.3@5.3.28-9
  • Fixed in: 5.3.28-9+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* db5.3/libdb5.3@5.3.28-9

Overview

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory.

References

high severity

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.17.27

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* dpkg@1.17.27

Overview

dpkg-source in dpkg 1.3.0 through 1.18.23 is able to use a non-GNU patch program and does not offer a protection mechanism for blank-indented diff hunks, which allows remote attackers to conduct directory traversal attacks via a crafted Debian source package, as demonstrated by use of dpkg-source on NetBSD.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.1.0-6+deb8u3
  • Fixed in: 2.1.0-6+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* expat/libexpat1@2.1.0-6+deb8u3

Overview

An integer overflow during the parsing of XML using the Expat library. This vulnerability affects Firefox < 50.

References

high severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.1.0-6+deb8u3
  • Fixed in: 2.1.0-6+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* expat/libexpat1@2.1.0-6+deb8u3

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.1.0-6+deb8u3
  • Fixed in: 2.1.0-6+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* expat/libexpat1@2.1.0-6+deb8u3

Overview

XML External Entity vulnerability in libexpat 2.2.0 and earlier (Expat XML Parser Library) allows attackers to put the parser in an infinite loop using a malformed external entity definition from an external DTD.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.1.0-6+deb8u3
  • Fixed in: 2.1.0-6+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* expat/libexpat1@2.1.0-6+deb8u3

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

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.5.2-3+deb8u2
  • Fixed in: 2.5.2-3+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* freetype/libfreetype6@2.5.2-3+deb8u2

Overview

In FreeType before 2.6.1, a buffer over-read occurs in type1/t1parse.c on function T1_Get_Private_Dict where there is no check that the new values of cur and limit are sensible before going to Again.

References

high severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.5.2-3+deb8u2
  • Fixed in: 2.5.2-3+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* freetype/libfreetype6@2.5.2-3+deb8u2

Overview

FreeType before 2.6.1 has a heap-based buffer over-read in T1_Get_Private_Dict in type1/t1parse.c.

References

high severity

Information Exposure

  • Vulnerable module: gcc-4.8/gcc-4.8-base
  • Introduced through: gcc-4.8/gcc-4.8-base@4.8.4-1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.8/gcc-4.8-base@4.8.4-1

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

Information Exposure

  • Vulnerable module: gcc-4.9
  • Introduced through: gcc-4.9@4.9.2-10, gcc-4.9/cpp-4.9@4.9.2-10 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/cpp-4.9@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/gcc-4.9-base@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libasan1@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libatomic1@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libcilkrts5@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libgcc-4.9-dev@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libgcc1@1:4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libgomp1@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libitm1@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/liblsan0@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libquadmath0@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libstdc++6@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libtsan0@4.9.2-10
  • Introduced through: digitalmarketplace/base:1.0@* gcc-4.9/libubsan0@4.9.2-10

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u7

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

Overview

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

References

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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-1352, CVE-2019-1354, CVE-2019-1387.

References

high severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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-1352, CVE-2019-1387.

References

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u9

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u10

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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

Open Redirect

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

Overview

A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any program that exists on the victim's machine being executed. Such a URL could be placed in the .gitmodules file of a malicious project, and an unsuspecting victim could be tricked into running "git clone --recurse-submodules" to trigger the vulnerability.

References

high severity

OS Command Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

Overview

Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute arbitrary OS commands via shell metacharacters in a module name. The vulnerable code is reachable via git-shell even without CVS support.

References

high severity

Out-of-bounds Read

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3
  • Fixed in: 1:2.1.4-2.1+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

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

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: git
  • Introduced through: git@1:2.1.4-2.1+deb8u3 and git/git-man@1:2.1.4-2.1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* git@1:2.1.4-2.1+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* git/git-man@1:2.1.4-2.1+deb8u3

Overview

A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

References

high severity

Access Restriction Bypass

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

** DISPUTED ** GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat."

References

high severity

Improper Data Handling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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

Improper Resource Shutdown or Release

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or possibly unspecified other impact, as demonstrated by a crash in __memmove_avx_unaligned_erms in sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S during a memcpy.

References

high severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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

NULL Pointer Dereference

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

high severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others
  • Fixed in: 2.19-18+deb8u10

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

glibc contains a vulnerability that allows specially crafted LD_LIBRARY_PATH values to manipulate the heap/stack, causing them to alias, potentially resulting in arbitrary code execution. Please note that additional hardening changes have been made to glibc to prevent manipulation of stack and heap memory but these issues are not directly exploitable, as such they have not been given a CVE. This affects glibc 2.25 and earlier.

References

high severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

Multiple stack-based buffer overflows in the GNU C Library (aka glibc or libc6) before 2.23 allow context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a long argument to the (1) nan, (2) nanf, or (3) nanl function.

References

high severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

** DISPUTED ** GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat."

References

high severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

** DISPUTED ** In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern.

References

high severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

Overview

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

References

high severity

Untrusted Search Path

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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.19-18+deb8u9, glibc/libc-dev-bin@2.19-18+deb8u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc-dev-bin@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/libc6-dev@2.19-18+deb8u9
  • Introduced through: digitalmarketplace/base:1.0@* glibc/multiarch-support@2.19-18+deb8u9

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

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg
  • Introduced through: gnupg@1.4.18-7+deb8u3 and gnupg/gpgv@1.4.18-7+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gnupg@1.4.18-7+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* gnupg/gpgv@1.4.18-7+deb8u3

Overview

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg
  • Introduced through: gnupg@1.4.18-7+deb8u3 and gnupg/gpgv@1.4.18-7+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gnupg@1.4.18-7+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* gnupg/gpgv@1.4.18-7+deb8u3

Overview

A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.

References

high severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: gnupg
  • Introduced through: gnupg@1.4.18-7+deb8u3 and gnupg/gpgv@1.4.18-7+deb8u3
  • Fixed in: 1.4.18-7+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gnupg@1.4.18-7+deb8u3
  • Introduced through: digitalmarketplace/base:1.0@* gnupg/gpgv@1.4.18-7+deb8u3

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

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls-deb0-28
  • Introduced through: gnutls28/libgnutls-deb0-28@3.3.8-6+deb8u5
  • Fixed in: 3.3.8-6+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* gnutls28/libgnutls-deb0-28@3.3.8-6+deb8u5

Overview

GnuTLS version 3.5.12 and earlier is vulnerable to a NULL pointer dereference while decoding a status response TLS extension with valid contents. This could lead to a crash of the GnuTLS server application.

References

high severity

Buffer Overflow

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.2.39.3a460-3
  • Fixed in: 2:1.9.2.39.3a460-3+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* inetutils/inetutils-ping@2:1.9.2.39.3a460-3

Overview

utility.c in telnetd in netkit telnet through 0.17 allows remote attackers to execute arbitrary code via short writes or urgent data, because of a buffer overflow involving the netclear and nextitem functions.

References

high severity

Out-of-bounds Write

  • Vulnerable module: inetutils/inetutils-ping
  • Introduced through: inetutils/inetutils-ping@2:1.9.2.39.3a460-3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* inetutils/inetutils-ping@2:1.9.2.39.3a460-3

Overview

Insufficient validation of environment variables in the telnet client supplied in Junos OS can lead to stack-based buffer overflows, which can be exploited to bypass veriexec restrictions on Junos OS. A stack-based overflow is present in the handling of environment variables when connecting via the telnet client to remote telnet servers. This issue only affects the telnet client — accessible from the CLI or shell — in Junos OS. Inbound telnet services are not affected by this issue. This issue affects: Juniper Networks Junos OS: 12.3 versions prior to 12.3R12-S13; 12.3X48 versions prior to 12.3X48-D80; 14.1X53 versions prior to 14.1X53-D130, 14.1X53-D49; 15.1 versions prior to 15.1F6-S12, 15.1R7-S4; 15.1X49 versions prior to 15.1X49-D170; 15.1X53 versions prior to 15.1X53-D237, 15.1X53-D496, 15.1X53-D591, 15.1X53-D69; 16.1 versions prior to 16.1R3-S11, 16.1R7-S4; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R2-S7, 17.2R3-S1; 17.3 versions prior to 17.3R3-S4; 17.4 versions prior to 17.4R1-S6, 17.4R2-S3, 17.4R3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S3; 18.2 versions prior to 18.2R1-S5, 18.2R2-S2, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S3, 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2.

References

high severity

Double Free

  • Vulnerable module: krb5/krb5-multidev
  • Introduced through: krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2, krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssrpc4@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libk5crypto3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5clnt-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5srv-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkdb5-7@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5-3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5support0@1.12.1+dfsg-19+deb8u2

Overview

Double free vulnerability in MIT Kerberos 5 (aka krb5) allows attackers to have unspecified impact via vectors involving automatic deletion of security contexts on error.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/krb5-multidev
  • Introduced through: krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2, krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssrpc4@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libk5crypto3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5clnt-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5srv-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkdb5-7@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5-3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5support0@1.12.1+dfsg-19+deb8u2

Overview

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

References

high severity

Out-of-Bounds

  • Vulnerable module: krb5/krb5-multidev
  • Introduced through: krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2, krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* krb5/krb5-multidev@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssapi-krb5-2@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libgssrpc4@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libk5crypto3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5clnt-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkadm5srv-mit9@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkdb5-7@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5-3@1.12.1+dfsg-19+deb8u2
  • Introduced through: digitalmarketplace/base:1.0@* krb5/libkrb5support0@1.12.1+dfsg-19+deb8u2

Overview

plugins/preauth/pkinit/pkinit_crypto_openssl.c in MIT Kerberos 5 (aka krb5) through 1.15.2 mishandles Distinguished Name (DN) fields, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and application crash) in situations involving untrusted X.509 data, related to the get_matching_data and X509_NAME_oneline_ex functions. NOTE: this has security relevance only in use cases outside of the MIT Kerberos distribution, e.g., the use of get_matching_data in KDC certauth plugin code that is specific to Red Hat.

References

high severity

Out-of-Bounds

  • Vulnerable module: libffi/libffi-dev
  • Introduced through: libffi/libffi-dev@3.1-2+b2 and libffi/libffi6@3.1-2+b2
  • Fixed in: 3.1-2+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libffi/libffi-dev@3.1-2+b2
  • Introduced through: digitalmarketplace/base:1.0@* libffi/libffi6@3.1-2+b2

Overview

libffi requests an executable stack allowing attackers to more easily trigger arbitrary code execution by overwriting the stack. Please note that libffi is used by a number of other libraries. It was previously stated that this affects libffi version 3.2.1 but this appears to be incorrect. libffi prior to version 3.1 on 32 bit x86 systems was vulnerable, and upstream is believed to have fixed this issue in version 3.1.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.6.3-2+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgcrypt20@1.6.3-2+deb8u2

Overview

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

References

high severity

Double Free

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u11

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

Overview

Double free vulnerability in the gdImagePngPtr function in libgd2 before 2.2.5 allows remote attackers to cause a denial of service via vectors related to a palette with no colors.

References

high severity

Double Free

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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

NULL Pointer Dereference

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u14

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

Overview

gdImageClone in gd.c in libgd 2.1.0-rc2 through 2.2.5 has a NULL pointer dereference allowing attackers to crash an application via a specific function call sequence. Only affects PHP when linked with an external libgd (not bundled).

References

high severity

Out-of-bounds Read

  • Vulnerable module: libgd2/libgd3
  • Introduced through: libgd2/libgd3@2.1.0-5+deb8u9

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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.1.0-5+deb8u9
  • Fixed in: 2.1.0-5+deb8u12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libgd2/libgd3@2.1.0-5+deb8u9

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.29-1+deb8u2
  • Fixed in: 1.29-1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libidn/libidn11@1.29-1+deb8u2

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

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Overview

Affected versions of this package are vulnerable to Excessive Iteration libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

There is no fixed version for libjpeg-turbo.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12
  • Fixed in: 1:1.3.1-12+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Overview

The cjpeg utility in libjpeg allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) or execute arbitrary code via a crafted file.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

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

There is no fixed version for libjpeg-turbo.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Overview

In generate_jsimd_ycc_rgb_convert_neon of jsimd_arm64_neon.S, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution in an unprivileged process with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-120551338

References

high severity

Resource Exhaustion

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libjpeg-turbo/libjpeg62-turbo@1:1.3.1-12

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

There is no fixed version for libjpeg-turbo.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libpng/libpng12-0
  • Introduced through: libpng/libpng12-0@1.2.50-2+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libpng/libpng12-0@1.2.50-2+deb8u3

Overview

An issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

Overview

In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted 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.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1
  • Introduced through: libssh2/libssh2-1@1.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.4.3-4.1+deb8u1
  • Fixed in: 1.4.3-4.1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libssh2/libssh2-1@1.4.3-4.1+deb8u1

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.2-3+deb8u2
  • Fixed in: 4.2-3+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libtasn1-6@4.2-3+deb8u2

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

Out-of-Bounds

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.2-3+deb8u2
  • Fixed in: 4.2-3+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libtasn1-6@4.2-3+deb8u2

Overview

Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-based buffer overflow by tricking a user into processing a specially crafted assignments file via the e.g. asn1Coding utility.

References

high severity

Improper Input Validation

  • Vulnerable module: libvpx/libvpx1
  • Introduced through: libvpx/libvpx1@1.3.0-3
  • Fixed in: 1.3.0-3+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libvpx/libvpx1@1.3.0-3

Overview

A vulnerability in the Android media framework (libvpx) related to odd frame width. Product: Android. Versions: 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-64710201.

References

high severity

Numeric Errors

  • Vulnerable module: libvpx/libvpx1
  • Introduced through: libvpx/libvpx1@1.3.0-3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libvpx/libvpx1@1.3.0-3

Overview

Google Chrome before 43.0.2357.65 relies on libvpx code that was not built with an appropriate --size-limit value, which allows remote attackers to trigger a negative value for a size field, and consequently cause a denial of service or possibly have unspecified other impact, via a crafted frame size in VP9 video data.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libvpx/libvpx1
  • Introduced through: libvpx/libvpx1@1.3.0-3
  • Fixed in: 1.3.0-3+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libvpx/libvpx1@1.3.0-3

Overview

In libvpx, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-122675483

References

high severity

Out-of-bounds Read

  • Vulnerable module: libvpx/libvpx1
  • Introduced through: libvpx/libvpx1@1.3.0-3
  • Fixed in: 1.3.0-3+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libvpx/libvpx1@1.3.0-3

Overview

In vp8_decode_frame of decodeframe.c, there is a possible out of bounds read due to improper input validation. This could lead to remote information disclosure if error correction were turned on, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1Android ID: A-62458770

References

high severity

Access Restriction Bypass

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

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-6@2:1.6.2-3
  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-data@2:1.6.2-3

Overview

The XGetImage function in X.org libX11 before 1.6.4 might allow remote X servers to gain privileges via vectors involving image type and geometry, which triggers out-of-bounds read operations.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-6@2:1.6.2-3
  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-data@2:1.6.2-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

Off-by-one Error

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

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-6@2:1.6.2-3
  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-data@2:1.6.2-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.2-3 and libx11/libx11-data@2:1.6.2-3
  • Fixed in: 2:1.6.2-3+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-6@2:1.6.2-3
  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-data@2:1.6.2-3

Overview

The XListFonts function in X.org libX11 before 1.6.4 might allow remote X servers to gain privileges via vectors involving length fields, which trigger out-of-bounds write operations.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-6@2:1.6.2-3
  • Introduced through: digitalmarketplace/base:1.0@* libx11/libx11-data@2:1.6.2-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.1+dfsg1-5+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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.1+dfsg1-5+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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.1+dfsg1-5+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u8

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u7

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits) whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write about "size" many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2, such as PHP, to crash.

References

high severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a stack-based buffer overflow. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. At the end of the routine, the function may strcat two more characters without checking whether the current strlen(buf) + 2 < size. This vulnerability causes programs that use libxml2, such as PHP, to crash.

References

high severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling redirects.

References

high severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictAddString function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for CVE-2016-1839.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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 Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for libxml2 Bug 759398.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

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

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

A remote code execution vulnerability in libxml2 could enable an attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses this library. Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2. Android ID: A-37104170.

References

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

Use after free in libxml2 before 2.9.5, as used in Google Chrome prior to 63.0.3239.84 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1+dfsg1-5+deb8u4
  • Fixed in: 2.9.1+dfsg1-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxml2@2.9.1+dfsg1-5+deb8u4

Overview

A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution, DTD validation, external DTD subset loading, or default DTD attributes). Depending on the context, this may expose a higher-risk attack surface in libxml2 not usually reachable with default parser flags, and expose content from local files, HTTP, or FTP servers (which might be otherwise unreachable).

References

high severity

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

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u5

high severity

Improper Access Control

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u4

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxslt/libxslt1.1@1.1.28-2+deb8u3

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

Out-of-Bounds

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxslt/libxslt1.1@1.1.28-2+deb8u3

Overview

libxslt in Apple iOS before 9.3.3, OS X before 10.11.6, iTunes before 12.4.2 on Windows, iCloud before 5.2.1 on Windows, tvOS before 9.2.2, and watchOS before 2.2.2 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2016-4607, CVE-2016-4608, CVE-2016-4610, and CVE-2016-4612.

References

high severity

Out-of-Bounds

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxslt/libxslt1.1@1.1.28-2+deb8u3

Overview

libxslt in Apple iOS before 9.3.3, OS X before 10.11.6, iTunes before 12.4.2 on Windows, iCloud before 5.2.1 on Windows, tvOS before 9.2.2, and watchOS before 2.2.2 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2016-4607, CVE-2016-4608, CVE-2016-4609, and CVE-2016-4612.

References

high severity

Use After Free

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxslt/libxslt1.1@1.1.28-2+deb8u3

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.1
  • Introduced through: libxslt/libxslt1.1@1.1.28-2+deb8u3
  • Fixed in: 1.1.28-2+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* libxslt/libxslt1.1@1.1.28-2+deb8u3

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/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

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

Improper Input Validation

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

Overview

In ncurses 6.0, there is an attempted 0xffffffffffffffff access in the append_acs function of tinfo/parse_entry.c. It could lead to a remote denial of service attack if the terminfo library code is used to process untrusted terminfo data.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

Overview

There is an infinite loop in the next_char function in comp_scan.c in ncurses 6.0, related to libtic. A crafted input will lead to a remote denial of service attack.

References

high severity

NULL Pointer Dereference

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

Overview

In ncurses 6.0, 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 attack if the terminfo library code is used to process untrusted terminfo data.

References

high severity

Out-of-Bounds

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

Overview

In ncurses 6.0, there is a stack-based buffer overflow in the fmt_entry function. A crafted input will lead to a remote arbitrary code execution attack.

References

high severity

Out-of-Bounds

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u3

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

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

Use of Externally-Controlled Format String

  • Vulnerable module: ncurses/libncurses5
  • Introduced through: ncurses/libncurses5@5.9+20140913-1+b1, ncurses/libncursesw5@5.9+20140913-1+b1 and others
  • Fixed in: 5.9+20140913-1+deb8u1

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncurses5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libncursesw5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/libtinfo5@5.9+20140913-1+b1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-base@5.9+20140913-1
  • Introduced through: digitalmarketplace/base:1.0@* ncurses/ncurses-bin@5.9+20140913-1+b1

Overview

In ncurses 6.0, there is a format string vulnerability in the fmt_entry function. A crafted input will lead to a remote arbitrary code execution attack.

References

high severity

Access Restriction Bypass

  • Vulnerable module: nginx
  • Introduced through: nginx@1.6.2-5+deb8u4, nginx/nginx-common@1.6.2-5+deb8u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* nginx@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-common@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-full@1.6.2-5+deb8u4

Overview

The default configuration of nginx, possibly 1.3.13 and earlier, uses world-readable permissions for the (1) access.log and (2) error.log files, which allows local users to obtain sensitive information by reading the files.

References

high severity

HTTP Request Smuggling

  • Vulnerable module: nginx
  • Introduced through: nginx@1.6.2-5+deb8u4, nginx/nginx-common@1.6.2-5+deb8u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* nginx@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-common@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-full@1.6.2-5+deb8u4

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

Integer Overflow or Wraparound

  • Vulnerable module: nginx
  • Introduced through: nginx@1.6.2-5+deb8u4, nginx/nginx-common@1.6.2-5+deb8u4 and others
  • Fixed in: 1.6.2-5+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* nginx@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-common@1.6.2-5+deb8u4
  • Introduced through: digitalmarketplace/base:1.0@* nginx/nginx-full@1.6.2-5+deb8u4

Overview

Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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.10.3
  • Fixed in: 6.11.5

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

Overview

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

Affected versions fo this package are vulnerable to Denial of Service (DoS) attacks.

The windowBits parameter controls how much of a message zlib keeps in memory while compressing it. A larger "window", as it's called, means more opportunities to spot and compress repeated bits of text, but results in higher memory usage. windowBits is the base-2 logarithm of the size of this window in bytes, and previously could take any integer value from 8 to 15.

This problem (Node.js crashing or throwing an exception) could be remotely exploited using some of the existing WebSocket clients that may request a value of 8 for windowBits in certain cases or with a custom built WebSocket client. There may also exist other vectors through which a zLib operation would be initiated by a remote request with a window size that results in a value of windowBits of 8.

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 versions 4.8.5, 6.11.5, 8.8.0 or higher.

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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.10.3
  • Fixed in: 6.15.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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.10.3
  • Fixed in: 6.14.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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

Error Handling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

Overview

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

Affected versions of this package are vulnerable to Error Handling. When using the TLS or HTTP2 modules, an attacker could send application data in a way that bypassed TLS authentication and encryption.

Remediation

Upgrade node to version 4.8.7, 6.12.2, 8.9.3, 9.2.1 or higher.

References

high severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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

Information Exposure

  • Vulnerable module: node
  • Introduced through: node@6.10.3
  • Fixed in: 6.11.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

Overview

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

Affected versions of this package are vulnerable to Information Exposure. The function ares_parse_naptr_reply(), which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way.

Remediation

Upgrade node to version 4.8.4, 6.11.1, 7.10.1, 8.1.4 or higher.

References

high severity

Unprotected Primary Channel

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@1.0 node@6.10.3

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

Improper Authentication

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2
  • Fixed in: 2.4.40+dfsg-1+deb8u5

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2

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

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2

Overview

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

References

high severity

Resource Exhaustion

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2
  • Fixed in: 2.4.40+dfsg-1+deb8u6

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* openldap/libldap-2.4-2@2.4.40+dfsg-1+deb8u2

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

Key Management Errors

  • Vulnerable module: openssl
  • Introduced through: openssl@1.0.1t-1+deb8u6, openssl/libssl-dev@1.0.1t-1+deb8u6 and others
  • Fixed in: 1.0.1t-1+deb8u9

Detailed paths

  • Introduced through: digitalmarketplace/base:1.0@* openssl@1.0.1t-1+deb8u6
  • Introduced through: digitalmarketplace/base:1.0@* openssl/libssl-dev@1.0.1t-1+deb8u6
  • Introduced through: digitalmarketplace/base:1.0@* openssl/libssl1.0.0@1.0.1t-1+deb8u6