Docker hassioaddons/base:amd64-2.3.0

Vulnerabilities

21 via 30 paths

Dependencies

26

Source

Group 6 Copy Created with Sketch. Docker

Target OS

alpine:3.8.1
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 21
Status
  • 21
  • 0
  • 0

high severity

Buffer Overflow

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r3

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

high severity

Double Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r3

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

high severity

Out-of-Bounds

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r1

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

Overview

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

References

high severity

Out-of-bounds Read

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r2

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

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/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r2

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

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/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r1

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

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 Write

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r2

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

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

Use After Free

  • Vulnerable module: curl/curl
  • Introduced through: curl/curl@7.61.1-r0 and curl/libcurl@7.61.1-r0
  • Fixed in: 7.61.1-r1

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/curl@7.61.1-r0
  • Introduced through: hassioaddons/base:amd64-2.3.0@* curl/libcurl@7.61.1-r0

Overview

A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.9.0-r1

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

Overview

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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 Write

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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

Out-of-bounds Write

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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
  • Introduced through: libssh2/libssh2@1.8.0-r3
  • Fixed in: 1.8.1-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* libssh2/libssh2@1.8.0-r3

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: musl/musl
  • Introduced through: musl/musl@1.1.19-r10 and musl/musl-utils@1.1.19-r10
  • Fixed in: 1.1.19-r11

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* musl/musl@1.1.19-r10
  • Introduced through: hassioaddons/base:amd64-2.3.0@* musl/musl-utils@1.1.19-r10

Overview

musl libc through 1.1.23 has an x87 floating-point stack adjustment imbalance, related to the math/i386/ directory. In some cases, use of this library could introduce out-of-bounds writes that are not present in an application's source code.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.32.0-r0
  • Fixed in: 1.39.2-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* nghttp2/nghttp2-libs@1.32.0-r0

Overview

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

References

high severity

Resource Exhaustion

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.32.0-r0
  • Fixed in: 1.39.2-r0

Detailed paths

  • Introduced through: hassioaddons/base:amd64-2.3.0@* nghttp2/nghttp2-libs@1.32.0-r0

Overview

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

References