Vulnerability report for Docker golang:1.8-rc-stretch

Vulnerabilities	892 via 1690 paths
Dependencies	179
Source	Docker
Target OS	debian:unstable

Test your Docker Hub image against our market leading vulnerability database Sign up for free

Severity

Critical
99
High
270
Medium
191
Low
332

Status

Open
892
Patched
0
Ignored
0

critical severity

new

Embedded Malicious Code

Vulnerable module: xz-utils/liblzma5
Introduced through: xz-utils/liblzma5@5.2.2-1.2
Fixed in: 5.6.1+really5.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › xz-utils/liblzma5@5.2.2-1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Malicious code was discovered in the upstream tarballs of xz, starting with version 5.6.0. Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library.

Remediation

Upgrade Debian:unstable xz-utils to version 5.6.1+really5.4.5-1 or higher.

References

Embedded Malicious Code vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: apr/libapr1
Introduced through: apr/libapr1@1.5.2-5
Fixed in: 1.7.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › apr/libapr1@1.5.2-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream apr package and not the apr package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Integer Overflow or Wraparound vulnerability in apr_encode functions of Apache Portable Runtime (APR) allows an attacker to write beyond bounds of a buffer. This issue affects Apache Portable Runtime (APR) version 1.7.0.

Remediation

Upgrade Debian:unstable apr to version 1.7.2-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: bzip2/libbz2-1.0
Introduced through: bzip2/libbz2-1.0@1.0.6-8
Fixed in: 1.0.6-9.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › bzip2/libbz2-1.0@1.0.6-8

NVD Description

Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable bzip2 to version 1.0.6-9.1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Buffer Overflow

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.66.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

Remediation

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Buffer Overflow vulnerability report

critical severity

CVE-2018-1000007

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.58.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.58.0-1 or higher.

References

CVE-2018-1000007 vulnerability report

critical severity

Double Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.66.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

Remediation

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Double Free vulnerability report

critical severity

Exposure of Resource to Wrong Sphere

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously was used to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent POST request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Exposure of Resource to Wrong Sphere vulnerability report

critical severity

Incorrect Default Permissions

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.84.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally widen the permissions for the target file, leaving the updated file accessible to more users than intended.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Incorrect Default Permissions vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.62.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.)

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.57.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.57.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.62.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.57.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library.

Remediation

Upgrade Debian:unstable curl to version 7.57.0-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.57.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.57.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.64.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.60.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.60.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.61.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

Remediation

Upgrade Debian:unstable curl to version 7.61.0-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.3.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake.

When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes.

If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there.

The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Remediation

Upgrade Debian:unstable curl to version 8.3.0-3 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Use After Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.62.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Use After Free vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: db5.3/libdb5.3
Introduced through: db5.3/libdb5.3@5.3.28-12
Fixed in: 5.3.28+dfsg1-0.9

Detailed paths

Introduced through: golang@1.8-rc-stretch › db5.3/libdb5.3@5.3.28-12

NVD Description

Note: Versions mentioned in the description apply only to the upstream db5.3 package and not the db5.3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.

Remediation

Upgrade Debian:unstable db5.3 to version 5.3.28+dfsg1-0.9 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Directory Traversal

Vulnerable module: dpkg
Introduced through: dpkg@1.18.18 and dpkg/libdpkg-perl@1.18.18
Fixed in: 1.21.8

Detailed paths

Introduced through: golang@1.8-rc-stretch › dpkg@1.18.18
Introduced through: golang@1.8-rc-stretch › dpkg/libdpkg-perl@1.18.18

NVD Description

Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs.

Remediation

Upgrade Debian:unstable dpkg to version 1.21.8 or higher.

References

Directory Traversal vulnerability report

critical severity

Exposure of Resource to Wrong Sphere

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Exposure of Resource to Wrong Sphere vulnerability report

critical severity

Improper Encoding or Escaping of Output

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as checks for whether a UTF-8 character is valid in a certain context.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Improper Encoding or Escaping of Output vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-2 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Arbitrary Argument Injection

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.19.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable git to version 1:2.19.1-1 or higher.

References

Arbitrary Argument Injection vulnerability report

critical severity

CVE-2019-1353

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1353 vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.39.1-0.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a .gitattributes file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted .gitattributes file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.

Remediation

Upgrade Debian:unstable git to version 1:2.39.1-0.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.39.1-0.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is distributed revision control system. git log can display commits in an arbitrary format using its --format specifiers. This functionality is also exposed to git archive via the export-subst gitattribute. When processing the padding operators, there is a integer overflow in pretty.c::format_and_pad_commit() where a size_t is stored improperly as an int, and then added as an offset to a memcpy(). This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., git log --format=...). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable git archive in untrusted repositories. If you expose git archive via git daemon, disable it by running git config --global daemon.uploadArch false.

Remediation

Upgrade Debian:unstable git to version 1:2.39.1-0.1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Untrusted Search Path

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.19.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if '.' were at the end of $PATH) in certain cases involving the run_command() API and run-command.c, because there was a dangerous change from execvp to execv during 2017.

Remediation

Upgrade Debian:unstable git to version 1:2.19.2-1 or higher.

References

Untrusted Search Path vulnerability report

critical severity

Race Condition

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.58.3-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2.0 package and not the glib2.0 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

file_copy_fallback in gio/gfile.c in GNOME GLib 2.15.0 through 2.61.1 does not properly restrict file permissions while a copy operation is in progress. Instead, default permissions are used.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.3-2 or higher.

References

Race Condition vulnerability report

critical severity

Buffer Overflow

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.33-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Debian:unstable glibc to version 2.33-3 or higher.

References

Buffer Overflow vulnerability report

critical severity

Buffer Overflow

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.33-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its path argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Debian:unstable glibc to version 2.33-3 or higher.

References

Buffer Overflow vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.27-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.27-3 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.28-9 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.27-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.27-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.27-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.27-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Use After Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.32-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free. It may use the notification thread attributes object (passed through its struct sigevent parameter) after it has been freed by the caller, leading to a denial of service (application crash) or possibly unspecified other impact.

Remediation

Upgrade Debian:unstable glibc to version 2.32-1 or higher.

References

Use After Free vulnerability report

critical severity

Double Free

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attackers to have unspecified impact via crafted policy language information in an X.509 certificate with a Proxy Certificate Information extension.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-1 or higher.

References

Double Free vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

Multiple heap-based buffer overflows in the read_attribute function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allow remote attackers to have unspecified impact via a crafted OpenPGP certificate.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

Stack-based buffer overflow in the cdk_pk_get_keyid function in lib/opencdk/pubkey.c in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attackers to have unspecified impact via a crafted OpenPGP certificate.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Use After Free

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A flaw was found in gnutls. A use after free issue in client sending key_share extension may lead to memory corruption and other consequences.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.1-1 or higher.

References

Use After Free vulnerability report

critical severity

Use After Free

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.1-1 or higher.

References

Use After Free vulnerability report

critical severity

Double Free

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 57.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream icu package and not the icu package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Double free in i18n/zonemeta.cpp in International Components for Unicode (ICU) for C/C++ through 59.1 allows remote attackers to execute arbitrary code via a crafted string, aka a "redundant UVector entry clean up function call" issue.

Remediation

Upgrade Debian:unstable icu to version 57.1-7 or higher.

References

Double Free vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 63.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

International Components for Unicode (ICU) for C/C++ 63.1 has an integer overflow in number::impl::DecimalQuantity::toScientificString() in i18n/number_decimalquantity.cpp.

Remediation

Upgrade Debian:unstable icu to version 63.1-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Buffer Overflow

Vulnerable module: inetutils/inetutils-ping
Introduced through: inetutils/inetutils-ping@2:1.9.4-2+b1
Fixed in: 2:1.9.4-12

Detailed paths

Introduced through: golang@1.8-rc-stretch › inetutils/inetutils-ping@2:1.9.4-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream inetutils package and not the inetutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable inetutils to version 2:1.9.4-12 or higher.

References

Buffer Overflow vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: libidn/libidn11
Introduced through: libidn/libidn11@1.33-1
Fixed in: 1.33-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libidn/libidn11@1.33-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libidn package and not the libidn package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable libidn to version 1.33-2 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: lz4/liblz4-1
Introduced through: lz4/liblz4-1@0.0~r131-2
Fixed in: 1.9.3-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › lz4/liblz4-1@0.0~r131-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream lz4 package and not the lz4 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

There's a flaw in lz4. An attacker who submits a crafted file to an application linked with lz4 may be able to trigger an integer overflow, leading to calling of memmove() on a negative size argument, causing an out-of-bounds write and/or a crash. The greatest impact of this flaw is to availability, with some potential impact to confidentiality and integrity as well.

Remediation

Upgrade Debian:unstable lz4 to version 1.9.3-2 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.6.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream mercurial package and not the mercurial package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

mpatch.c in Mercurial before 4.6.1 mishandles integer addition and subtraction, aka OVE-20180430-0002.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

OS Command Injection

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.3.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

Mercurial prior to 4.3 did not adequately sanitize hostnames passed to ssh, leading to possible shell-injection attacks.

Remediation

Upgrade Debian:unstable mercurial to version 4.3.1-1 or higher.

References

OS Command Injection vulnerability report

critical severity

OS Command Injection

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.4.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the form of a .git/hooks/post-update script checked into the repository. Typical use of Mercurial prevents construction of such repositories, but they can be created programmatically.

Remediation

Upgrade Debian:unstable mercurial to version 4.4.1-1 or higher.

References

OS Command Injection vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170708-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170708-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Use of Externally-Controlled Format String

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170701-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170701-1 or higher.

References

Use of Externally-Controlled Format String vulnerability report

critical severity

SQL Injection

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.5.12+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping.

Remediation

Upgrade Debian:unstable openldap to version 2.5.12+dfsg-1 or higher.

References

SQL Injection vulnerability report

critical severity

CVE-2023-28531

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.3p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.

Remediation

Upgrade Debian:unstable openssh to version 1:9.3p1-1 or higher.

References

CVE-2023-28531 vulnerability report

critical severity

Unquoted Search Path or Element

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.3p2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

Remediation

Upgrade Debian:unstable openssh to version 1:9.3p2-1 or higher.

References

Unquoted Search Path or Element vulnerability report

critical severity

Buffer Overflow

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1l-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1l-1 or higher.

References

Buffer Overflow vulnerability report

critical severity

OS Command Injection

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1o-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1o-1 or higher.

References

OS Command Injection vulnerability report

critical severity

OS Command Injection

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

Remediation

Upgrade Debian:unstable openssl to version 3.0.4-1 or higher.

References

OS Command Injection vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.4-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys running on machines supporting AVX512IFMA instructions of the X86_64 architecture are affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.4-2 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.28.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Perl before 5.26.3 and 5.28.0 before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

Remediation

Upgrade Debian:unstable perl to version 5.28.1-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.28.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Perl before 5.26.3 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

Remediation

Upgrade Debian:unstable perl to version 5.28.0-3 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.28.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Perl before 5.26.3 and 5.28.x before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.

Remediation

Upgrade Debian:unstable perl to version 5.28.1-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

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

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

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

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:3.3.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable shadow to version 1:4.5-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

CVE-2017-2519

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.16.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in certain Apple products. iOS before 10.3.2 is affected. macOS before 10.12.5 is affected. tvOS before 10.2.1 is affected. watchOS before 3.2.2 is affected. The issue involves the "SQLite" component. It allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted SQL statement.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.16.0-1 or higher.

References

CVE-2017-2519 vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

In SQLite 3.31.1, there is an out of bounds access problem through ALTER TABLE for views that have a nested FROM clause.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.19.3-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

The getNodeSize function in ext/rtree/rtree.c in SQLite through 3.19.3, as used in GDAL and other products, mishandles undersized RTree blobs in a crafted database, leading to a heap-based buffer over-read or possibly unspecified other impact.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.19.3-3 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.16.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

An issue was discovered in certain Apple products. iOS before 10.3.2 is affected. macOS before 10.12.5 is affected. tvOS before 10.2.1 is affected. watchOS before 3.2.2 is affected. The issue involves the "SQLite" component. It allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and application crash) via a crafted SQL statement.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.16.2-1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Improper Input Validation

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.9.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream subversion package and not the subversion package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A maliciously constructed svn+ssh:// URL would cause Subversion clients before 1.8.19, 1.9.x before 1.9.7, and 1.10.0.x through 1.10.0-alpha3 to run an arbitrary shell command. Such a URL could be generated by a malicious server, by a malicious user committing to a honest server (to attack another user of that server's repositories), or by a proxy server. The vulnerability affects all clients, including those that use file://, http://, and plain (untunneled) svn://.

Remediation

Upgrade Debian:unstable subversion to version 1.9.7-1 or higher.

References

Improper Input Validation vulnerability report

critical severity

Use After Free

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 240-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later.

Remediation

Upgrade Debian:unstable systemd to version 240-1 or higher.

References

Use After Free vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.20.1-1.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

Remediation

Upgrade Debian:unstable wget to version 1.20.1-1.1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: zlib/zlib1g
Introduced through: zlib/zlib1g@1:1.2.8.dfsg-4
Fixed in: 1:1.3.dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › zlib/zlib1g@1:1.2.8.dfsg-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.

Remediation

Upgrade Debian:unstable zlib to version 1:1.3.dfsg-2 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Write

Vulnerable module: zlib/zlib1g
Introduced through: zlib/zlib1g@1:1.2.8.dfsg-4
Fixed in: 1:1.2.11.dfsg-4.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › zlib/zlib1g@1:1.2.8.dfsg-4

NVD Description

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Remediation

Upgrade Debian:unstable zlib to version 1:1.2.11.dfsg-4.1 or higher.

References

Out-of-bounds Write vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality fail when multiple URLs are requested serially. Using its HSTS support, curl can be instructed to use HTTPS instead of usingan insecure clear-text HTTP step even when HTTP is provided in the URL. ThisHSTS mechanism would however surprisingly be ignored by subsequent transferswhen done on the same command line because the state would not be properlycarried on.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

critical severity

Double Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it again.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Double Free vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.56.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.56.1-1 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.58.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl 7.49.0 to and including 7.57.0 contains an out bounds read in code handling HTTP/2 trailers. It was reported (https://github.com/curl/curl/pull/2231) that reading an HTTP/2 trailer could mess up future trailers since the stored size was one byte less than required. The problem is that the code that creates HTTP/1-like headers from the HTTP/2 trailer data once appended a string like : to the target buffer, while this was recently changed to : (a space was added after the colon) but the following math wasn't updated correspondingly. When accessed, the data is read out of bounds and causes either a crash or that the (too large) data gets passed to client write. This could lead to a denial-of-service situation or an information disclosure if someone has a service that echoes back or uses the trailers for something.

Remediation

Upgrade Debian:unstable curl to version 7.58.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.60.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.62.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.62.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.60.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Integer Overflow or Wraparound

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-13

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The wordexp function in the GNU C Library (aka glibc) through 2.33 may crash or read arbitrary memory in parse_param (in posix/wordexp.c) when called with an untrusted, crafted pattern, potentially resulting in a denial of service or disclosure of information. This occurs because atoi was used but strtoul should have been used to ensure correct calculations.

Remediation

Upgrade Debian:unstable glibc to version 2.31-13 or higher.

References

Integer Overflow or Wraparound vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libbsd/libbsd0
Introduced through: libbsd/libbsd0@0.8.3-1
Fixed in: 0.10.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libbsd/libbsd0@0.8.3-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libbsd package and not the libbsd package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable libbsd to version 0.10.0-1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Read vulnerability report

critical severity

Off-by-one Error

Vulnerable module: libtasn1-6
Introduced through: libtasn1-6@4.9-4
Fixed in: 4.19.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libtasn1-6@4.9-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.19.0-2 or higher.

References

Off-by-one Error vulnerability report

critical severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.5.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

Mercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in Unauthorized data access. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 4.5.1.

Remediation

Upgrade Debian:unstable mercurial to version 4.5.2-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

critical severity

Out-of-Bounds

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.0-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Buffer overflow in the S_grok_bslash_N function in regcomp.c in Perl 5 before 5.24.3-RC1 and 5.26.x before 5.26.1-RC1 allows remote attackers to disclose sensitive information or cause a denial of service (application crash) via a crafted regular expression with an invalid '\N{U+...}' escape.

Remediation

Upgrade Debian:unstable perl to version 5.26.0-8 or higher.

References

Out-of-Bounds vulnerability report

critical severity

Out-of-bounds Read

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.28.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Perl before 5.26.3 has a buffer over-read via a crafted regular expression that triggers disclosure of sensitive information from process memory.

Remediation

Upgrade Debian:unstable perl to version 5.28.0-3 or higher.

References

Out-of-bounds Read vulnerability report

high severity

CVE-2017-14176

Vulnerable module: bzr
Introduced through: bzr@2.7.0+bzr6619-4 and bzr/python-bzrlib@2.7.0+bzr6619-4
Fixed in: 2.7.0+bzr6622-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › bzr@2.7.0+bzr6619-4
Introduced through: golang@1.8-rc-stretch › bzr/python-bzrlib@2.7.0+bzr6619-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream bzr package and not the bzr package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Bazaar through 2.7.0, when Subprocess SSH is used, allows remote attackers to execute arbitrary commands via a bzr+ssh URL with an initial dash character in the hostname, a related issue to CVE-2017-9800, CVE-2017-12836, CVE-2017-12976, CVE-2017-16228, CVE-2017-1000116, and CVE-2017-1000117.

Remediation

Upgrade Debian:unstable bzr to version 2.7.0+bzr6622-7 or higher.

References

CVE-2017-14176 vulnerability report

high severity

Arbitrary Code Injection

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Directory Traversal

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Directory Traversal vulnerability report

high severity

SQL Injection

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-2
Introduced through: golang@1.8-rc-stretch › cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream cyrus-sasl2 package and not the cyrus-sasl2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

In Cyrus SASL 2.1.17 through 2.1.27 before 2.1.28, plugins/sql.c does not escape the password for a SQL INSERT or UPDATE statement.

Remediation

Upgrade Debian:unstable cyrus-sasl2 to version 2.1.28+dfsg-2 or higher.

References

SQL Injection vulnerability report

high severity

Incorrect Calculation

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts function in xmlparse.c can lead to realloc misbehavior (e.g., allocating too few bytes, or only freeing memory).

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Incorrect Calculation vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

CVE-2017-8386

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.11.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

git-shell in git before 2.4.12, 2.5.x before 2.5.6, 2.6.x before 2.6.7, 2.7.x before 2.7.5, 2.8.x before 2.8.5, 2.9.x before 2.9.4, 2.10.x before 2.10.3, 2.11.x before 2.11.2, and 2.12.x before 2.12.3 might allow remote authenticated users to gain privileges via a repository name that starts with a - (dash) character.

Remediation

Upgrade Debian:unstable git to version 1:2.11.0-3 or higher.

References

CVE-2017-8386 vulnerability report

high severity

CVE-2019-1387

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1387 vulnerability report

high severity

Heap-based Buffer Overflow

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.38.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.

Remediation

Upgrade Debian:unstable git to version 1:2.38.1-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Open Redirect

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.14.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.14.1-1 or higher.

References

Open Redirect vulnerability report

high severity

OS Command Injection

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.14.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.14.2-1 or higher.

References

OS Command Injection vulnerability report

high severity

Use After Free

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.66.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

A vulnerability was found in GNOME gvdb. It has been classified as critical. This affects the function gvdb_table_write_contents_async of the file gvdb-builder.c. The manipulation leads to use after free. It is possible to initiate the attack remotely. The name of the patch is d83587b2a364eb9a9a53be7e6a708074e252de14. It is recommended to apply a patch to fix this issue. The identifier VDB-216789 was assigned to this vulnerability.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.0-1 or higher.

References

Use After Free vulnerability report

high severity

Cross-site Request Forgery (CSRF)

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2
Fixed in: 2.2.12-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.12-1 or higher.

References

Cross-site Request Forgery (CSRF) vulnerability report

high severity

Improper Input Validation

Vulnerable module: gzip
Introduced through: gzip@1.6-5
Fixed in: 1.12-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gzip@1.6-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Debian:unstable gzip to version 1.12-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Double Free

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 67.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

Double free in ICU in Google Chrome prior to 91.0.4472.77 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Debian:unstable icu to version 67.1-7 or higher.

References

Double Free vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 63.2-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

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

Remediation

Upgrade Debian:unstable icu to version 63.2-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.20.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Debian:unstable krb5 to version 1.20.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.8.0-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.8.0-2.1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-Bounds

Vulnerable module: libtasn1-6
Introduced through: libtasn1-6@4.9-4
Fixed in: 4.10-1.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libtasn1-6@4.9-4

NVD Description

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.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.10-1.1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.3.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and consequently execute arbitrary code, by using --debugger as a repository name.

Remediation

Upgrade Debian:unstable mercurial to version 4.3.1-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

high severity

Arbitrary Code Injection

Vulnerable module: sensible-utils
Introduced through: sensible-utils@0.0.9
Fixed in: 0.0.11

Detailed paths

Introduced through: golang@1.8-rc-stretch › sensible-utils@0.0.9

NVD Description

Note: Versions mentioned in the description apply only to the upstream sensible-utils package and not the sensible-utils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable sensible-utils to version 0.0.11 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-Bounds

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 239-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 239-11 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-Bounds

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.19.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

The retr.c:fd_read_body() function is called when processing OK responses. When the response is sent chunked in wget before 1.19.2, the chunk parser uses strtol() to read each chunk's length, but doesn't check that the chunk length is a non-negative number. The code then tries to read the chunk in pieces of 8192 bytes by using the MIN() macro, but ends up passing the negative chunk length to retr.c:fd_read(). As fd_read() takes an int argument, the high 32 bits of the chunk length are discarded, leaving fd_read() with a completely attacker controlled length argument. The attacker can corrupt malloc metadata after the allocated buffer.

Remediation

Upgrade Debian:unstable wget to version 1.19.2-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-Bounds

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.19.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

The http.c:skip_short_body() function is called in some circumstances, such as when processing redirects. When the response is sent chunked in wget before 1.19.2, the chunk parser uses strtol() to read each chunk's length, but doesn't check that the chunk length is a non-negative number. The code then tries to skip the chunk in pieces of 512 bytes by using the MIN() macro, but ends up passing the negative chunk length to connect.c:fd_read(). As fd_read() takes an int argument, the high 32 bits of the chunk length are discarded, leaving fd_read() with a completely attacker controlled length argument.

Remediation

Upgrade Debian:unstable wget to version 1.19.2-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Improper Input Validation

Vulnerable module: xz-utils/liblzma5
Introduced through: xz-utils/liblzma5@5.2.2-1.2
Fixed in: 5.2.5-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › xz-utils/liblzma5@5.2.2-1.2

NVD Description

Remediation

Upgrade Debian:unstable xz-utils to version 5.2.5-2.1 or higher.

References

Improper Input Validation vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.30.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.30.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2019-3462

Vulnerable module: apt
Introduced through: apt@1.4~beta3 and apt/libapt-pkg5.0@1.4~beta3
Fixed in: 1.8.0~alpha3.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › apt@1.4~beta3
Introduced through: golang@1.8-rc-stretch › apt/libapt-pkg5.0@1.4~beta3

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable apt to version 1.8.0~alpha3.1 or higher.

References

CVE-2019-3462 vulnerability report

high severity

Double Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Double Free vulnerability report

high severity

Heap-based Buffer Overflow

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.52.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.52.1-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Missing Authentication for Critical Function

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).

Remediation

Upgrade Debian:unstable curl to version 7.83.0-1 or higher.

References

Missing Authentication for Critical Function vulnerability report

high severity

Use of Incorrectly-Resolved Name or Reference

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A use of incorrectly resolved name vulnerability fixed in 7.83.1 might remove the wrong file when --no-clobber is used together with --remove-on-error.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

high severity

Use After Free

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.8-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

Remediation

Upgrade Debian:unstable expat to version 2.4.8-2 or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.9.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.9.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: nettle/libhogweed4
Introduced through: nettle/libhogweed4@3.3-1 and nettle/libnettle6@3.3-1
Fixed in: 3.7.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nettle/libhogweed4@3.3-1
Introduced through: golang@1.8-rc-stretch › nettle/libnettle6@3.3-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nettle package and not the nettle package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in Nettle in versions before 3.7.2, where several Nettle signature verification functions (GOST DSA, EDDSA & ECDSA) result in the Elliptic Curve Cryptography point (ECC) multiply function being called with out-of-range scalers, possibly resulting in incorrect results. This flaw allows an attacker to force an invalid signature, causing an assertion failure or possible validation. The highest threat to this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:unstable nettle to version 3.7.2-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

Improper Certificate Validation

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.38.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.

Remediation

Upgrade Debian:unstable perl to version 5.38.2-2 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.25.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.25.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.25.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.25.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0. A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote code execution. An attacker can send a malicious SQL command to trigger this vulnerability.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-3 or higher.

References

Use After Free vulnerability report

high severity

Improper Input Validation

Vulnerable module: bash
Introduced through: bash@4.4-2
Fixed in: 4.4-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › bash@4.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream bash package and not the bash package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The path autocompletion feature in Bash 4.4 allows local users to gain privileges via a crafted filename starting with a " (double quote) character and a command substitution metacharacter.

Remediation

Upgrade Debian:unstable bash to version 4.4-3 or higher.

References

Improper Input Validation vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: bash
Introduced through: bash@4.4-2
Fixed in: 5.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › bash@4.4-2

NVD Description

A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems.

Remediation

Upgrade Debian:unstable bash to version 5.2-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

Improper Input Validation vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.30-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.30-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-11 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-8 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.1-2 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-8 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-8 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-8 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-8 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Use After Free vulnerability report

high severity

Arbitrary Code Injection

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.72.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.64.0-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2017-10140

Vulnerable module: db5.3/libdb5.3
Introduced through: db5.3/libdb5.3@5.3.28-12
Fixed in: 5.3.28-13.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › db5.3/libdb5.3@5.3.28-12

NVD Description

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.

Remediation

Upgrade Debian:unstable db5.3 to version 5.3.28-13.1 or higher.

References

CVE-2017-10140 vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: e2fsprogs
Introduced through: e2fsprogs@1.43.3-1, e2fsprogs/e2fslibs@1.43.3-1 and others
Fixed in: 1.46.6~rc1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › e2fsprogs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/e2fslibs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libcomerr2@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libss2@1.43.3-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream e2fsprogs package and not the e2fsprogs package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem.

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.46.6~rc1-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for m_groupSize.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Arbitrary Code Injection

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.40.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Directory Traversal

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.17.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.17.1-1 or higher.

References

Directory Traversal vulnerability report

high severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x before 2.24.1 because a "git submodule update" operation can run commands found in the .gitmodules file of a malicious repository.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Ownership Management

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.37.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.

Remediation

Upgrade Debian:unstable git to version 1:2.37.2-1 or higher.

References

Improper Ownership Management vulnerability report

high severity

Uncontrolled Search Path Element

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.35.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users working on multi-user machines, where untrusted parties have write access to the same hard disk. Those untrusted parties could create the folder C:\.git, which would be picked up by Git operations run supposedly outside a repository while searching for a Git directory. Git would then respect any config in said Git directory. Git Bash users who set GIT_PS1_SHOWDIRTYSTATE are vulnerable as well. Users who installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are vulnerable: simply creating a new project would already read and respect the config specified in C:\.git\config. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder .git on all drives where Git commands are run, and remove read/write access from those folders as a workaround. Alternatively, define or extend GIT_CEILING_DIRECTORIES to cover the parent directory of the user profile, e.g. C:\Users if the user profile is located in C:\Users\my-user-name.

Remediation

Upgrade Debian:unstable git to version 1:2.35.2-1 or higher.

References

Uncontrolled Search Path Element vulnerability report

high severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.25-5 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

high severity

Off-by-one Error

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.33-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in glibc. An off-by-one buffer overflow and underflow in getcwd() may lead to memory corruption when the size of the buffer is exactly 1. A local attacker who can control the input buffer and size passed to getcwd() in a setuid program could use this flaw to potentially execute arbitrary code and escalate their privileges on the system.

Remediation

Upgrade Debian:unstable glibc to version 2.33-4 or higher.

References

Off-by-one Error vulnerability report

high severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.24-12

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.24-12 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.26-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.26-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-12

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A buffer overflow was discovered in the GNU C Library's dynamic loader ld.so while processing the GLIBC_TUNABLES environment variable. This issue could allow a local attacker to use maliciously crafted GLIBC_TUNABLES environment variables when launching binaries with SUID permission to execute code with elevated privileges.

Remediation

Upgrade Debian:unstable glibc to version 2.37-12 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-15

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when the openlog function was not called, or called with the ident argument set to NULL, and the program name (the basename of argv[0]) is bigger than 1024 bytes, resulting in an application crash or local privilege escalation. This issue affects glibc 2.36 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Untrusted Search Path

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.25-6 or higher.

References

Untrusted Search Path vulnerability report

high severity

Unchecked Return Value

Vulnerable module: inetutils/inetutils-ping
Introduced through: inetutils/inetutils-ping@2:1.9.4-2+b1
Fixed in: 2:2.4-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › inetutils/inetutils-ping@2:1.9.4-2+b1

NVD Description

GNU inetutils before 2.5 may allow privilege escalation because of unchecked return values of set*id() family functions in ftpd, rcp, rlogin, rsh, rshd, and uucpd. This is, for example, relevant if the setuid system call fails when a process is trying to drop privileges before letting an ordinary user control the activities of the process.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.4-3 or higher.

References

Unchecked Return Value vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20171125-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20171125-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.4-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Debian:unstable ncurses to version 6.4-3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Improper Verification of Cryptographic Signature

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.36.0-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

CPAN 2.28 allows Signature Verification Bypass.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-4 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.36.0-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

A vulnerability was found in perl. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-10 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Untrusted Search Path

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.32.1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Encode.pm, as distributed in Perl through 5.34.0, allows local users to gain privileges via a Trojan horse Encode::ConfigLocal library (in the current working directory) that preempts dynamic module loading. Exploitation requires an unusual configuration, and certain 2021 versions of Encode.pm (3.05 through 3.11). This issue occurs because the || operator evaluates @INC in a scalar context, and thus @INC has only an integer value.

Remediation

Upgrade Debian:unstable perl to version 5.32.1-5 or higher.

References

Untrusted Search Path vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:3.3.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Improper Privilege Management

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

The Debian shadow package before 1:4.5-1 for Shadow incorrectly lists pts/0 and pts/1 as physical terminals in /etc/securetty. This allows local users to login as password-less users even if they are connected by non-physical means such as SSH (hence bypassing PAM's nullok_secure configuration). This notably affects environments such as virtual machines automatically generated with a default blank root password, allowing all local users to escalate privileges.

Remediation

Upgrade Debian:unstable shadow to version 1:4.5-1 or higher.

References

Improper Privilege Management vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

Integer overflow in shadow 4.2.1 allows local users to gain privileges via crafted input to newuidmap.

Remediation

Upgrade Debian:unstable shadow to version 1:4.4-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 240-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 240-4 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 240-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 240-4 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2023-26604

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 247.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" command may be executed. Specifically, systemd does not set LESSSECURE to 1, and thus other programs may be launched from the less program. This presents a substantial security risk when running systemctl from Sudo, because less executes as root when the terminal size is too small to show the complete systemctl output.

Remediation

Upgrade Debian:unstable systemd to version 247.1-2 or higher.

References

CVE-2023-26604 vulnerability report

high severity

Deserialization of Untrusted Data

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 239-12

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 239-12 or higher.

References

Deserialization of Untrusted Data vulnerability report

high severity

Incorrect Privilege Assignment

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 242-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 242-4 or higher.

References

Incorrect Privilege Assignment vulnerability report

high severity

Privilege Chaining

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 242-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 242-4 or higher.

References

Privilege Chaining vulnerability report

high severity

Use After Free

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 244.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 244.2-1 or higher.

References

Use After Free vulnerability report

high severity

Access Restriction Bypass

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.31.1-0.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable util-linux to version 2.31.1-0.1 or higher.

References

Access Restriction Bypass vulnerability report

high severity

CVE-2018-7738

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.31.1-0.5

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

Remediation

Upgrade Debian:unstable util-linux to version 2.31.1-0.5 or higher.

References

CVE-2018-7738 vulnerability report

high severity

Information Exposure

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.20.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

Remediation

Upgrade Debian:unstable wget to version 1.20.1-1 or higher.

References

Information Exposure vulnerability report

high severity

Buffer Overflow

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution.

In a TLS client, this can be triggered by connecting to a malicious server.

In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Note: Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible.

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

Buffer Overflow vulnerability report

high severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

Improper Input Validation vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.3.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

Remediation

Upgrade Debian:unstable curl to version 8.3.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) .. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-3 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

high severity

CVE-2022-27775

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead.

Remediation

Upgrade Debian:unstable curl to version 7.83.0-1 or higher.

References

CVE-2022-27775 vulnerability report

high severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.74.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verification of the OCSP response.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.52.1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range.

Remediation

Upgrade Debian:unstable curl to version 7.52.1-5 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Information Exposure

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.72.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.62.0 through 7.70.0 is vulnerable to an information disclosure vulnerability that can lead to a partial password being leaked over the network and to the DNS server(s).

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Information Exposure vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.60.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

Remediation

Upgrade Debian:unstable curl to version 7.60.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.56.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.56.1-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.64.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.64.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.74.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Server-Side Request Forgery (SSRF)

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a different URL usingthe wrong host name when it is later retrieved.For example, a URL like http://example.com%2F127.0.0.1/, would be allowed bythe parser and get transposed into http://example.com/127.0.0.1/. This flawcan be used to circumvent filters, checks and more.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

high severity

Use After Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

Use After Free vulnerability report

high severity

Use After Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.72.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.

Remediation

Upgrade Debian:unstable curl to version 7.72.0-1 or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Write

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-2
Introduced through: golang@1.8-rc-stretch › cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-2

NVD Description

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.

Remediation

Upgrade Debian:unstable cyrus-sasl2 to version 2.1.27+dfsg-2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.3-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function.

Remediation

Upgrade Debian:unstable expat to version 2.4.3-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in copyString.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.2.7-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable expat to version 2.2.7-2 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Resource Exhaustion

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.6.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.

Remediation

Upgrade Debian:unstable expat to version 2.6.0-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

Use After Free

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.5.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situations.

Remediation

Upgrade Debian:unstable expat to version 2.5.0-1 or higher.

References

Use After Free vulnerability report

high severity

XML External Entity (XXE) Injection

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.2.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable expat to version 2.2.1-1 or higher.

References

XML External Entity (XXE) Injection vulnerability report

high severity

XML External Entity (XXE) Injection

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.2.6-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

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).

Remediation

Upgrade Debian:unstable expat to version 2.2.6-2 or higher.

References

XML External Entity (XXE) Injection vulnerability report

high severity

CVE-2021-40330

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.30.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected cross-protocol requests, as demonstrated by the git://localhost:1234/%0d%0a%0d%0aGET%20/%20HTTP/1.1 substring.

Remediation

Upgrade Debian:unstable git to version 1:2.30.1-1 or higher.

References

CVE-2021-40330 vulnerability report

high severity

Directory Traversal

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.39.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

Remediation

Upgrade Debian:unstable git to version 1:2.39.2-1 or higher.

References

Directory Traversal vulnerability report

high severity

Directory Traversal

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.40.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

Directory Traversal vulnerability report

high severity

Insufficiently Protected Credentials

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.26.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.26.1-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Insufficiently Protected Credentials

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.26.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.26.2-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Link Following

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.30.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. before cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

Remediation

Upgrade Debian:unstable git to version 1:2.30.2-1 or higher.

References

Link Following vulnerability report

high severity

Incorrect Conversion between Numeric Types

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.66.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

An issue was discovered in GNOME GLib before 2.66.7 and 2.67.x before 2.67.4. If g_byte_array_new_take() was called with a buffer of 4GB or more on a 64-bit platform, the length would be truncated modulo 2**32, causing unintended length truncation.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.7-1 or higher.

References

Incorrect Conversion between Numeric Types vulnerability report

high severity

Incorrect Conversion between Numeric Types

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.66.6-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

An issue was discovered in GNOME GLib before 2.66.6 and 2.67.x before 2.67.3. The function g_bytes_new has an integer overflow on 64-bit platforms due to an implicit cast from 64 bits to 32 bits. The overflow could potentially lead to memory corruption.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.6-1 or higher.

References

Incorrect Conversion between Numeric Types vulnerability report

high severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.60.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using g_file_make_directory_with_parents (kfsb->dir, NULL, NULL) and files using g_file_replace_contents (kfsb->file, contents, length, NULL, FALSE, G_FILE_CREATE_REPLACE_DESTINATION, NULL, NULL, NULL). Consequently, it does not properly restrict directory (and file) permissions. Instead, for directories, 0777 permissions are used; for files, default file permissions are used. This is similar to CVE-2019-12450.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.60.5-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

high severity

Resource Exhaustion

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.74.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

A flaw was found in GLib. GVariant deserialization fails to validate that the input conforms to the expected format, leading to denial of service.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

Improper Data Handling

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

Improper Data Handling vulnerability report

high severity

Improper Input Validation

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

In the GNU C Library (aka glibc or libc6) through 2.28, attempting to resolve a crafted hostname via getaddrinfo() leads to the allocation of a socket descriptor that is not closed. This is related to the if_nametoindex() function.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Memory Leak

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in the GNU C Library. A recent fix for CVE-2023-4806 introduced the potential for a memory leak, which may result in an application crash.

Remediation

Upgrade Debian:unstable glibc to version 2.37-11 or higher.

References

Memory Leak vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.33-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in glibc. The realpath() function can mistakenly return an unexpected value, potentially leading to information leakage and disclosure of sensitive data.

Remediation

Upgrade Debian:unstable glibc to version 2.33-4 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-15

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

An off-by-one heap-based buffer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a message bigger than INT_MAX bytes, leading to an incorrect calculation of the buffer size to store the message, resulting in an application crash. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Reachable Assertion

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.31-10 or higher.

References

Reachable Assertion vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: gmp/libgmp10
Introduced through: gmp/libgmp10@2:6.1.2+dfsg-1
Fixed in: 2:6.2.1+dfsg-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › gmp/libgmp10@2:6.1.2+dfsg-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gmp package and not the gmp package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

GNU Multiple Precision Arithmetic Library (GMP) through 6.2.1 has an mpz/inp_raw.c integer overflow and resultant buffer overflow via crafted input, leading to a segmentation fault on 32-bit platforms.

Remediation

Upgrade Debian:unstable gmp to version 2:6.2.1+dfsg-3 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Use of Incorrectly-Resolved Name or Reference

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2
Fixed in: 2.2.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

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.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.8-1 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

high severity

Access of Uninitialized Pointer

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.7-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.7-2 or higher.

References

Access of Uninitialized Pointer vulnerability report

high severity

Double Free

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.7.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.7-1 or higher.

References

Double Free vulnerability report

high severity

Double Free

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.7-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

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

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.7-2 or higher.

References

Double Free vulnerability report

high severity

Improper Verification of Cryptographic Signature

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.8.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A vulnerability was found in GnuTLS, where a cockpit (which uses gnuTLS) rejects a certificate chain with distributed trust. This issue occurs when validating a certificate chain with cockpit-certificate-ensure. This flaw allows an unauthenticated, remote client or attacker to initiate a denial of service attack.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.3-1 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Information Exposure

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.8.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.3-1 or higher.

References

Information Exposure vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

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.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-6 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

The stream reading functions in lib/opencdk/read-packet.c in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allow remote attackers to cause a denial of service (out-of-memory error and crash) via a crafted OpenPGP certificate.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.8-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

GnuTLS before 2017-02-20 has an out-of-bounds write caused by an integer overflow and heap-based buffer overflow related to the cdk_pkt_read function in opencdk/read-packet.c. This issue (which is a subset of the vendor's GNUTLS-SA-2017-3 report) is fixed in 3.5.10.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.8-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

An issue was discovered in GnuTLS before 3.6.15. A server can trigger a NULL pointer dereference in a TLS 1.3 client if a no_renegotiation alert is sent with unexpected timing, and then an invalid second handshake occurs. The crash happens in the application's error handling path, where the gnutls_deinit function is called after detecting a handshake failure.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.15-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 57.1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

International Components for Unicode (ICU) for C/C++ before 2017-02-13 has an out-of-bounds write caused by a heap-based buffer overflow related to the utf8TextAccess function in common/utext.cpp and the utext_setNativeIndex* function.

Remediation

Upgrade Debian:unstable icu to version 57.1-6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 57.1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

Remediation

Upgrade Debian:unstable icu to version 57.1-6 or higher.

References

Out-of-bounds Write vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: inetutils/inetutils-ping
Introduced through: inetutils/inetutils-ping@2:1.9.4-2+b1
Fixed in: 2:2.3-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › inetutils/inetutils-ping@2:1.9.4-2+b1

NVD Description

telnetd in GNU Inetutils through 2.3, MIT krb5-appl through 1.0.3, and derivative works has a NULL pointer dereference via 0xff 0xf7 or 0xff 0xf8. In a typical installation, the telnetd application would crash but the telnet service would remain available through inetd. However, if the telnetd application has many crashes within a short time interval, the telnet service would become unavailable after inetd logs a "telnet/tcp server failing (looping), service terminated" error. NOTE: MIT krb5-appl is not supported upstream but is shipped by a few Linux distributions. The affected code was removed from the supported MIT Kerberos 5 (aka krb5) product many years ago, at version 1.8.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.3-5 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.18.3-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to cause a NULL pointer dereference and daemon crash. This occurs because a return value is not properly managed in a certain situation.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-6 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Uncontrolled Recursion

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.18.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

MIT Kerberos 5 (aka krb5) before 1.17.2 and 1.18.x before 1.18.3 allows unbounded recursion via an ASN.1-encoded Kerberos message because the lib/krb5/asn.1/asn1_encode.c support for BER indefinite lengths lacks a recursion limit.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-1 or higher.

References

Uncontrolled Recursion vulnerability report

high severity

Information Exposure

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.9.4-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.9.4-2 or higher.

References

Information Exposure vulnerability report

high severity

Information Exposure

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.7.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

Libgcrypt before 1.8.1 does not properly consider Curve25519 side-channel attacks, which makes it easier for attackers to discover a secret key, related to cipher/ecc.c and mpi/ec.c.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.7.9-1 or higher.

References

Information Exposure vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.10.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

An issue was discovered in function _libssh2_packet_add in libssh2 1.10.0 allows attackers to access out of bounds memory.

Remediation

Upgrade Debian:unstable libssh2 to version 1.10.0-2 or higher.

References

Out-of-bounds Write vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: libtasn1-6
Introduced through: libtasn1-6@4.9-4
Fixed in: 4.12-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libtasn1-6@4.9-4

NVD Description

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.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.12-2.1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Uncontrolled Recursion

Vulnerable module: libtasn1-6
Introduced through: libtasn1-6@4.9-4
Fixed in: 4.13-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libtasn1-6@4.9-4

NVD Description

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

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.13-2 or higher.

References

Uncontrolled Recursion vulnerability report

high severity

Improper Input Validation

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.6.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

The mpatch_apply function in mpatch.c in Mercurial before 4.6.1 incorrectly proceeds in cases where the fragment start is past the end of the original data, aka OVE-20180430-0004.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.6.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

The mpatch_decode function in mpatch.c in Mercurial before 4.6.1 mishandles certain situations where there should be at least 12 bytes remaining after the current position in the patch data, but actually are not, aka OVE-20180430-0001.

Remediation

Upgrade Debian:unstable mercurial to version 4.6.1-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Link Following

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.3.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

Mercurial prior to version 4.3 is vulnerable to a missing symlink check that can malicious repositories to modify files outside the repository

Remediation

Upgrade Debian:unstable mercurial to version 4.3.1-1 or higher.

References

Link Following vulnerability report

high severity

Improper Input Validation

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170701-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170701-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170701-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

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.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170701-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Improper Input Validation

Vulnerable module: nettle/libhogweed4
Introduced through: nettle/libhogweed4@3.3-1 and nettle/libnettle6@3.3-1
Fixed in: 3.7.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nettle/libhogweed4@3.3-1
Introduced through: golang@1.8-rc-stretch › nettle/libnettle6@3.3-1

NVD Description

A flaw was found in the way nettle's RSA decryption functions handled specially crafted ciphertext. An attacker could use this flaw to provide a manipulated ciphertext leading to application crash and denial of service.

Remediation

Upgrade Debian:unstable nettle to version 3.7.3-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.39.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.39.2-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

CVE-2019-9513

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.39.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.39.2-1 or higher.

References

CVE-2019-9513 vulnerability report

high severity

Improper Enforcement of Message or Data Structure

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.41.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.41.0-1 or higher.

References

Improper Enforcement of Message or Data Structure vulnerability report

high severity

Resource Exhaustion

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.57.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.57.0-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

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

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

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

high severity

CVE-2020-36226

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

CVE-2020-36226 vulnerability report

high severity

Double Free

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Double Free vulnerability report

high severity

Integer Underflow

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Integer Underflow vulnerability report

high severity

Integer Underflow

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Integer Underflow vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.55+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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

Remediation

Upgrade Debian:unstable openldap to version 2.4.55+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.5.16+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

Remediation

Upgrade Debian:unstable openldap to version 2.5.16+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Reachable Assertion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.56+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was found in OpenLDAP. This flaw allows an attacker who can send a malicious packet to be processed by OpenLDAP’s slapd server, to trigger an assertion failure. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable openldap to version 2.4.56+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.56+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was found in OpenLDAP in versions before 2.4.56. This flaw allows an attacker who sends a malicious packet processed by OpenLDAP to force a failed assertion in csnNormalize23(). The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable openldap to version 2.4.56+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Reachable Assertion vulnerability report

high severity

Reachable Assertion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-2 or higher.

References

Reachable Assertion vulnerability report

high severity

Release of Invalid Pointer or Reference

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.57+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Debian:unstable openldap to version 2.4.57+dfsg-1 or higher.

References

Release of Invalid Pointer or Reference vulnerability report

high severity

Resource Exhaustion

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.50+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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).

Remediation

Upgrade Debian:unstable openldap to version 2.4.50+dfsg-1 or higher.

References

Resource Exhaustion vulnerability report

high severity

CVE-2023-5363

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.12-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.

Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes.

When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.

For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse.

Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical.

Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary.

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.12-1 or higher.

References

CVE-2023-5363 vulnerability report

high severity

Double Free

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.

The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.

These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.

The OpenSSL asn1parse command line application is also impacted by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Double Free vulnerability report

high severity

Improper Certificate Validation

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

A security vulnerability has been identified in all supported versions

of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.

Policy processing is disabled by default but can be enabled by passing the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Improper Input Validation

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0e-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

During a renegotiation handshake if the Encrypt-Then-Mac extension is negotiated where it was not in the original handshake (or vice-versa) then this can cause OpenSSL 1.1.0 before 1.1.0e to crash (dependent on ciphersuite). Both clients and servers are affected.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0e-1 or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Locking

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.7-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy processing being enabled on a publicly facing server is not considered to be a common setup.

Policy processing is enabled by passing the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Update (31 March 2023): The description of the policy processing enablement was corrected based on CVE-2023-0466.

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-2 or higher.

References

Improper Locking vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1j-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1j-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1n-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1n-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions.

The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack.

The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash.

The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.

PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attack.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0d-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1g-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1g-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0d-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Use After Free

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.

This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Use After Free vulnerability report

high severity

Integer Overflow or Wraparound

Vulnerable module: p11-kit/libp11-kit0
Introduced through: p11-kit/libp11-kit0@0.23.3-2
Fixed in: 0.23.22-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › p11-kit/libp11-kit0@0.23.3-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: p11-kit/libp11-kit0
Introduced through: p11-kit/libp11-kit0@0.23.3-2
Fixed in: 0.23.22-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › p11-kit/libp11-kit0@0.23.3-2

NVD Description

An issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-Bounds

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2
Fixed in: 2:8.39-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libpcre1 in PCRE 8.40 and libpcre2 in PCRE2 10.23 allow remote attackers to cause a denial of service (segmentation violation for read access, and application crash) by triggering an invalid Unicode property lookup.

Remediation

Upgrade Debian:unstable pcre3 to version 2:8.39-3 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2
Fixed in: 2:8.39-2.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

The compile_bracket_matchingpath function in pcre_jit_compile.c in PCRE through 8.x before revision 1680 (e.g., the PHP 7.1.1 bundled version) allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted regular expression.

Remediation

Upgrade Debian:unstable pcre3 to version 2:8.39-2.1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Buffer Overflow

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.30.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

Remediation

Upgrade Debian:unstable perl to version 5.30.3-1 or higher.

References

Buffer Overflow vulnerability report

high severity

Link Following

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.2-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

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

Remediation

Upgrade Debian:unstable perl to version 5.26.2-6 or higher.

References

Link Following vulnerability report

high severity

Out-of-Bounds

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.0-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Heap-based buffer overflow in the S_regatom function in regcomp.c in Perl 5 before 5.24.3-RC1 and 5.26.x before 5.26.1-RC1 allows remote attackers to cause a denial of service (out-of-bounds write) via a regular expression with a '\N{}' escape and the case-insensitive modifier.

Remediation

Upgrade Debian:unstable perl to version 5.26.0-8 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.26.1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

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

Remediation

Upgrade Debian:unstable perl to version 5.26.1-6 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Heap-based Buffer Overflow

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:3.3.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Heap-based Buffer Overflow vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:3.3.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Out-of-bounds Write vulnerability report

high severity

CVE-2019-19603

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.30.1 mishandles certain SELECT statements with a nonexistent VIEW, leading to an application crash.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

CVE-2019-19603 vulnerability report

high severity

CVE-2019-19959

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for example) valgrind.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

CVE-2019-19959 vulnerability report

high severity

Improper Handling of Exceptional Conditions

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Improper Handling of Exceptional Conditions vulnerability report

high severity

Improper Initialization

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.31.1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.31.1-5 or higher.

References

Improper Initialization vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

In SQlite 3.31.1, a potential null pointer derreference was found in the INTERSEC query processing.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.22.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.22.0-2 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results).

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.31.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated column optimizations.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.31.1-3 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.36.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

An issue found in SQLite SQLite3 v.3.35.4 that allows a remote attacker to cause a denial of service via the appendvfs.c function.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.36.0-2 or higher.

References

Out-of-bounds Read vulnerability report

high severity

SQL Injection

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.25.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.25.2, when queries are run on a table with a malformed PRIMARY KEY, allows remote attackers to cause a denial of service (application crash) by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases).

Remediation

Upgrade Debian:unstable sqlite3 to version 3.25.3-1 or higher.

References

SQL Injection vulnerability report

high severity

Unrestricted Upload of File with Dangerous Type

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Unrestricted Upload of File with Dangerous Type vulnerability report

high severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.32.2 has a use-after-free in resetAccumulator in select.c because the parse tree rewrite for window functions is too late.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.2-2 or higher.

References

Use After Free vulnerability report

high severity

Access of Uninitialized Pointer

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.10.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

Subversion's mod_dav_svn Apache HTTPD module versions 1.11.0 and 1.10.0 to 1.10.3 will crash after dereferencing an uninitialized pointer if the client omits the root path in a recursive directory listing operation.

Remediation

Upgrade Debian:unstable subversion to version 1.10.4-1 or higher.

References

Access of Uninitialized Pointer vulnerability report

high severity

Improper Input Validation

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.10.6-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a client sends certain sequences of protocol commands. This can lead to disruption for users of the server.

Remediation

Upgrade Debian:unstable subversion to version 1.10.6-1 or higher.

References

Improper Input Validation vulnerability report

high severity

NULL Pointer Dereference

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.14.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

Subversion's mod_authz_svn module will crash if the server is using in-repository authz rules with the AuthzSVNReposRelativeAccessFile option and a client sends a request for a non-existing repository URL. This can lead to disruption for users of the service. This issue was fixed in mod_dav_svn+mod_authz_svn servers 1.14.1 and mod_dav_svn+mod_authz_svn servers 1.10.7

Remediation

Upgrade Debian:unstable subversion to version 1.14.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

high severity

Use After Free

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.14.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

Subversion's mod_dav_svn is vulnerable to memory corruption. While looking up path-based authorization rules, mod_dav_svn servers may attempt to use memory which has already been freed. Affected Subversion mod_dav_svn servers 1.10.0 through 1.14.1 (inclusive). Servers that do not use mod_dav_svn are not affected.

Remediation

Upgrade Debian:unstable subversion to version 1.14.2-1 or higher.

References

Use After Free vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 255.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

Remediation

Upgrade Debian:unstable systemd to version 255.4-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Improper Input Validation

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 232-24

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd-resolved through 233 allows remote attackers to cause a denial of service (daemon crash) via a crafted DNS response with an empty question section.

Remediation

Upgrade Debian:unstable systemd to version 232-24 or higher.

References

Improper Input Validation vulnerability report

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 235-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 235-3 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 233-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small. A malicious DNS server can exploit this via a response with a specially crafted TCP payload to trick systemd-resolved into allocating a buffer that's too small, and subsequently write arbitrary data beyond the end of it.

Remediation

Upgrade Debian:unstable systemd to version 233-10 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: zlib/zlib1g
Introduced through: zlib/zlib1g@1:1.2.8.dfsg-4
Fixed in: 1:1.2.11.dfsg-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › zlib/zlib1g@1:1.2.8.dfsg-4

NVD Description

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Debian:unstable zlib to version 1:1.2.11.dfsg-4 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Information Exposure

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.7.8-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.8-5 or higher.

References

Information Exposure vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.13-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.13-2 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.14-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TLS server always uses wrong data in place of an encryption key derived from an application.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.14-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

high severity

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

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

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

high severity

Improper Certificate Validation

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1k-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

Improper Certificate Validation vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1l-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1l-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

CVE-2022-46908

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.40.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite through 3.40.0, when relying on --safe for execution of an untrusted CLI script, does not properly implement the azProhibitedFunctions protection mechanism, and instead allows UDF functions such as WRITEFILE.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.40.0-2 or higher.

References

CVE-2022-46908 vulnerability report

high severity

Out-of-Bounds

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.43.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.1-1 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: apr/libapr1
Introduced through: apr/libapr1@1.5.2-5
Fixed in: 1.7.0-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › apr/libapr1@1.5.2-5

NVD Description

An out-of-bounds array read in the apr_time_exp*() functions was fixed in the Apache Portable Runtime 1.6.3 release (CVE-2017-12613). The fix for this issue was not carried forward to the APR 1.7.x branch, and hence version 1.7.0 regressed compared to 1.6.3 and is vulnerable to the same issue.

Remediation

Upgrade Debian:unstable apr to version 1.7.0-7 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Read

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.3+20220423-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.

Remediation

Upgrade Debian:unstable ncurses to version 6.3+20220423-1 or higher.

References

Out-of-bounds Read vulnerability report

high severity

Double Free

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:8.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.

Remediation

Upgrade Debian:unstable openssh to version 1:8.4p1-5 or higher.

References

Double Free vulnerability report

high severity

Buffer Overflow

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

An attacker can craft a malicious email address to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service).

Remediation

Upgrade Debian:unstable openssl to version 3.0.7-1 or higher.

References

Buffer Overflow vulnerability report

high severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.25-5 or higher.

References

Out-of-Bounds vulnerability report

high severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.30-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.30-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.30-3 or higher.

References

Use After Free vulnerability report

high severity

Improper Privilege Management

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:8.7p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.

Remediation

Upgrade Debian:unstable openssh to version 1:8.7p1-1 or higher.

References

Improper Privilege Management vulnerability report

high severity

Inclusion of Functionality from Untrusted Control Sphere

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:3.3.15-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

Remediation

Upgrade Debian:unstable procps to version 2:3.3.15-1 or higher.

References

Inclusion of Functionality from Untrusted Control Sphere vulnerability report

high severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

Use After Free vulnerability report

high severity

Improper Authorization

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 241-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 241-3 or higher.

References

Improper Authorization vulnerability report

high severity

Race Condition

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 239-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

A race condition in chown_one() of systemd allows an attacker to cause systemd to set arbitrary permissions on arbitrary files. Affected releases are systemd versions up to and including 239.

Remediation

Upgrade Debian:unstable systemd to version 239-11 or higher.

References

Race Condition vulnerability report

medium severity

Cryptographic Issues

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.7.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.7.8-1 or higher.

References

Cryptographic Issues vulnerability report

medium severity

Improper Encoding or Escaping of Output

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:7.9p1-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

An issue was discovered in OpenSSH 7.9. Due to missing character encoding in the progress display, a malicious server (or Man-in-The-Middle attacker) can employ crafted object names to manipulate the client output, e.g., by using ANSI control codes to hide additional files being transferred. This affects refresh_progress_meter() in progressmeter.c.

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-6 or higher.

References

Improper Encoding or Escaping of Output vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: e2fsprogs
Introduced through: e2fsprogs@1.43.3-1, e2fsprogs/e2fslibs@1.43.3-1 and others
Fixed in: 1.45.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › e2fsprogs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/e2fslibs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libcomerr2@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libss2@1.43.3-1

NVD Description

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

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.4-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: e2fsprogs
Introduced through: e2fsprogs@1.43.3-1, e2fsprogs/e2fslibs@1.43.3-1 and others
Fixed in: 1.45.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › e2fsprogs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/e2fslibs@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libcomerr2@1.43.3-1
Introduced through: golang@1.8-rc-stretch › e2fsprogs/libss2@1.43.3-1

NVD Description

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

Remediation

Upgrade Debian:unstable e2fsprogs to version 1.45.5-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: apr-util/libaprutil1
Introduced through: apr-util/libaprutil1@1.5.4-3
Fixed in: 1.6.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › apr-util/libaprutil1@1.5.4-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream apr-util package and not the apr-util package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Integer Overflow or Wraparound vulnerability in apr_base64 functions of Apache Portable Runtime Utility (APR-util) allows an attacker to write beyond bounds of a buffer.

This issue affects Apache Portable Runtime Utility (APR-util) 1.6.1 and prior versions.

Remediation

Upgrade Debian:unstable apr-util to version 1.6.3-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29-5 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.84.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functionality to behave incorrectly when multiple URLs are requested in parallel. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This HSTS mechanism would however surprisingly fail when multiple transfers are done in parallel as the HSTS cache file gets overwritten by the most recentlycompleted transfer. A later HTTP-only transfer to the earlier host name would then not get upgraded properly to HSTS.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

medium severity

CVE-2023-46218

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.5.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.

It could do this by exploiting a mixed case flaw in curl's function that verifies a given cookie domain against the Public Suffix List (PSL). For example a cookie could be set with domain=co.UK when the URL used a lower case hostname curl.co.uk, even though co.uk is listed as a PSL domain.

Remediation

Upgrade Debian:unstable curl to version 8.5.0-1 or higher.

References

CVE-2023-46218 vulnerability report

medium severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.52.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).

Remediation

Upgrade Debian:unstable curl to version 7.52.1-3 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Information Exposure

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.55.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The endto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. Limit curl's redirect protocols with --proto-redir and libcurl's with CURLOPT_REDIR_PROTOCOLS.

Remediation

Upgrade Debian:unstable curl to version 7.55.0-1 or higher.

References

Information Exposure vulnerability report

medium severity

Insufficiently Protected Credentials

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Remediation

Upgrade Debian:unstable curl to version 7.83.0-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.55.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl supports "globbing" of URLs, in which a user can pass a numerical range to have the tool iterate over those numbers to do a sequence of transfers. In the globbing function that parses the numerical range, there was an omission that made curl read a byte beyond the end of the URL if given a carefully crafted, or just wrongly written, URL. The URL is stored in a heap based buffer, so it could then be made to wrongly read something else instead of crashing. An example of a URL that triggers the flaw would be http://ur%20[0-60000000000000000000.

Remediation

Upgrade Debian:unstable curl to version 7.55.0-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl can be told to parse a .netrc file for credentials. If that file endsin a line with 4095 consecutive non-white space letters and no newline, curlwould first read past the end of the stack-based buffer, and if the readworks, write a zero byte beyond its boundary.This will in most cases cause a segfault or similar, but circumstances might also cause different outcomes.If a malicious user can provide a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-of-service.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Uncontrolled Recursion

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

In Expat (aka libexpat) before 2.4.5, an attacker can trigger stack exhaustion in build_model via a large nesting depth in the DTD element.

Remediation

Upgrade Debian:unstable expat to version 2.4.5-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.

Remediation

Upgrade Debian:unstable glibc to version 2.37-9 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Arbitrary Code Injection

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2
Fixed in: 2.2.35-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.35-3 or higher.

References

Arbitrary Code Injection vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.7.3-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A NULL pointer dereference flaw was found in GnuTLS. As Nettle's hash update functions internally call memcpy, providing zero-length input may cause undefined behavior. This flaw leads to a denial of service after authentication in rare circumstances.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.7.3-2 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 57.1-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

Integer overflow in international date handling in International Components for Unicode (ICU) for C/C++ before 60.1, as used in V8 in Google Chrome prior to 63.0.3239.84 and other products, allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

Remediation

Upgrade Debian:unstable icu to version 57.1-9 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Insufficient Verification of Data Authenticity

Vulnerable module: inetutils/inetutils-ping
Introduced through: inetutils/inetutils-ping@2:1.9.4-2+b1
Fixed in: 2:2.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › inetutils/inetutils-ping@2:1.9.4-2+b1

NVD Description

The ftp client in GNU Inetutils before 2.2 does not validate addresses returned by PASV/LSPV responses to make sure they match the server address. This is similar to CVE-2020-8284 for curl.

Remediation

Upgrade Debian:unstable inetutils to version 2:2.2-1 or higher.

References

Insufficient Verification of Data Authenticity vulnerability report

medium severity

Access of Uninitialized Pointer

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.20.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

Remediation

Upgrade Debian:unstable krb5 to version 1.20.1-3 or higher.

References

Access of Uninitialized Pointer vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.18.3-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field.

Remediation

Upgrade Debian:unstable krb5 to version 1.18.3-7 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.16.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

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

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Reachable Assertion

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.15.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

In MIT Kerberos 5 (aka krb5) 1.7 and later, an authenticated attacker can cause a KDC assertion failure by sending invalid S4U2Self or S4U2Proxy requests.

Remediation

Upgrade Debian:unstable krb5 to version 1.15.1-2 or higher.

References

Reachable Assertion vulnerability report

medium severity

CVE-2023-50495

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.4+20230625-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Remediation

Upgrade Debian:unstable ncurses to version 6.4+20230625-1 or higher.

References

CVE-2023-50495 vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170701-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

In ncurses, possibly a 6.x version, there is a NULL pointer dereference at the function _nc_name_match that will lead to a denial of service attack. NOTE: the original report stated version 6.1, but the issue did not reproduce for that version according to the maintainer or a reliable third-party

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170701-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the function dump_uses() in progs/dump_entry.c in ncurses 6.0 that might lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the function _nc_read_entry_source() in progs/tic.c in ncurses 6.0 that might lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the _nc_safe_strcat function in strings.c in ncurses 6.0 that will lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170902-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the fmt_entry function in progs/dump_entry.c in ncurses 6.0 that might lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170902-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the function postprocess_termcap() in parse_entry.c in ncurses 6.0 that will lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.0+20170827-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is an illegal address access in the _nc_save_str function in alloc_entry.c in ncurses 6.0. It will lead to a remote denial of service attack.

Remediation

Upgrade Debian:unstable ncurses to version 6.0+20170827-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in one_one_mapping function in progs/dump_entry.c:1373 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1116 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in _nc_find_entry in tinfo/comp_hash.c:70 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in _nc_find_entry function in tinfo/comp_hash.c:66 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in fmt_entry function in progs/dump_entry.c:1100 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

Buffer Overflow vulnerability in postprocess_terminfo function in tinfo/parse_entry.c:997 in ncurses 6.1 allows remote attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Double Free

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

servers/slapd/back-mdb/search.c in OpenLDAP through 2.4.44 is prone to a double free vulnerability. A user with access to search the directory can crash slapd by issuing a search including the Paged Results control with a page size of 0.

Remediation

Upgrade Debian:unstable openldap to version 2.4.44+dfsg-5 or higher.

References

Double Free vulnerability report

medium severity

Double Free

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.2p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH server (sshd) 9.1 introduced a double-free vulnerability during options.kex_algorithms handling. This is fixed in OpenSSH 9.2. The double free can be leveraged, by an unauthenticated remote attacker in the default configuration, to jump to any location in the sshd address space. One third-party report states "remote code execution is theoretically possible."

Remediation

Upgrade Debian:unstable openssh to version 1:9.2p1-1 or higher.

References

Double Free vulnerability report

medium severity

OS Command Injection

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.6p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

OS Command Injection vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0g-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0g-1 or higher.

References

Information Exposure vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.1.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Uncontrolled Recursion

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0h-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service attack. There are no such structures used within SSL/TLS that come from untrusted sources so this is considered safe. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected 1.0.2b-1.0.2n).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Divide By Zero

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.29.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.29.0-2 or higher.

References

Divide By Zero vulnerability report

medium severity

Improper Input Validation

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.10.6-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a well-formed read-only request produces a particular answer. This can lead to disruption for users of the server.

Remediation

Upgrade Debian:unstable subversion to version 1.10.6-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Improper Input Validation

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.19.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

Remediation

Upgrade Debian:unstable wget to version 1.19.5-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Race Condition

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.8.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

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

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.5-1 or higher.

References

Race Condition vulnerability report

medium severity

CRLF Injection

Vulnerable module: wget
Introduced through: wget@1.18-4
Fixed in: 1.19.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

CRLF injection vulnerability in the url_parse function in url.c in Wget through 1.19.1 allows remote attackers to inject arbitrary HTTP headers via CRLF sequences in the host subcomponent of a URL.

Remediation

Upgrade Debian:unstable wget to version 1.19.1-2 or higher.

References

CRLF Injection vulnerability report

medium severity

Open Redirect

Vulnerable module: wget
Introduced through: wget@1.18-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › wget@1.18-4

NVD Description

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

Remediation

There is no fixed version for Debian:unstable wget.

References

Open Redirect vulnerability report

medium severity

Improper Verification of Cryptographic Signature

Vulnerable module: apt
Introduced through: apt@1.4~beta3 and apt/libapt-pkg5.0@1.4~beta3
Fixed in: 1.6.4

Detailed paths

Introduced through: golang@1.8-rc-stretch › apt@1.4~beta3
Introduced through: golang@1.8-rc-stretch › apt/libapt-pkg5.0@1.4~beta3

NVD Description

The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.

Remediation

Upgrade Debian:unstable apt to version 1.6.4 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

Inefficient Regular Expression Complexity

Vulnerable module: configobj/python-configobj
Introduced through: configobj/python-configobj@5.0.6-2
Fixed in: 5.0.8-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › configobj/python-configobj@5.0.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream configobj package and not the configobj package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

All versions of the package configobj are vulnerable to Regular Expression Denial of Service (ReDoS) via the validate function, using (.+?)((.*)).

Note: This is only exploitable in the case of a developer, putting the offending value in a server side configuration file.

Remediation

Upgrade Debian:unstable configobj to version 5.0.8-2 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

medium severity

Double Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Double Free vulnerability report

medium severity

Improper Authentication

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Authentication

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Insufficient Verification of Data Authenticity

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Insufficient Verification of Data Authenticity vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.84.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Use After Free

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.86.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Debian:unstable curl to version 7.86.0-3 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.62.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly to a target address instead of connecting via a proxy server when configured to do so, because the proxy_addr field is mishandled. This bug is timing-dependent and may occur only sporadically depending on network delays. The greatest security relevance is in use cases where a proxy is used to help with privacy/anonymity, even though there is no technical barrier to a direct connection. NOTE: versions before 2.60 are unaffected.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.62.5-1 or higher.

References

Information Exposure vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.25-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

Upgrade Debian:unstable glibc to version 2.31-9 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Use After Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.24-15

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

Use-after-free vulnerability in the clntudp_call function in sunrpc/clnt_udp.c in the GNU C Library (aka glibc or libc6) before 2.26 allows remote attackers to have unspecified impact via vectors related to error path.

Remediation

Upgrade Debian:unstable glibc to version 2.24-15 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.36-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Remediation

Upgrade Debian:unstable glibc to version 2.36-3 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.

Remediation

Upgrade Debian:unstable glibc to version 2.37-10 or higher.

References

Use After Free vulnerability report

medium severity

Information Exposure

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.8.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.2-1 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.19-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plain text recovery attacks via statistical analysis of timing data using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.19-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Information Exposure

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.7.6-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

In Libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-term secret key. 1.7.7 makes a cipher/ecc-eddsa.c change to store this session key in secure memory, to ensure that constant-time point operations are used in the MPI library.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.7.6-2 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.8.7-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.7-6 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Improper Validation of Integrity Check Value

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.11.0-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

Remediation

Upgrade Debian:unstable libssh2 to version 1.11.0-4 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

medium severity

Link Following

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

A flaw was found in Mercurial before 4.9. It was possible to use symlinks and subrepositories to defeat Mercurial's path-checking logic and write files outside a repository.

Remediation

Upgrade Debian:unstable mercurial to version 4.9-1 or higher.

References

Link Following vulnerability report

medium severity

Directory Traversal

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:7.9p1-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-9 or higher.

References

Directory Traversal vulnerability report

medium severity

Improper Validation of Integrity Check Value

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.6p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

medium severity

CVE-2021-4160

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1m-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1m-1 or higher.

References

CVE-2021-4160 vulnerability report

medium severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Information Exposure vulnerability report

medium severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0d-1 or higher.

References

Information Exposure vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1j-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1j-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1i-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1i-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1k-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1k-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: The AES-XTS cipher decryption implementation for 64 bit ARM platform contains a bug that could cause it to read past the input buffer, leading to a crash.

Impact summary: Applications that use the AES-XTS algorithm on the 64 bit ARM platform can crash in rare circumstances. The AES-XTS algorithm is usually used for disk encryption.

The AES-XTS cipher decryption implementation for 64 bit ARM platform will read past the end of the ciphertext buffer if the ciphertext size is 4 mod 5 in 16 byte blocks, e.g. 144 bytes or 1024 bytes. If the memory after the ciphertext buffer is unmapped, this will trigger a crash which results in a denial of service.

If an attacker can control the size and location of the ciphertext buffer being decrypted by an application using AES-XTS on 64 bit ARM, the application is affected. This is fairly unlikely making this issue a Low severity one.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1a-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1a-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1a-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Race Condition

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.24.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

Race condition in the rmtree and remove_tree functions in the File-Path module before 2.13 for Perl allows attackers to set the mode on arbitrary files via vectors involving directory-permission loosening logic.

Remediation

Upgrade Debian:unstable perl to version 5.24.1-3 or higher.

References

Race Condition vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

CVE-2023-7008

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 255.1-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

Remediation

Upgrade Debian:unstable systemd to version 255.1-3 or higher.

References

CVE-2023-7008 vulnerability report

medium severity

Race Condition

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 234-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

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

Remediation

Upgrade Debian:unstable systemd to version 234-1 or higher.

References

Race Condition vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: apt
Introduced through: apt@1.4~beta3 and apt/libapt-pkg5.0@1.4~beta3
Fixed in: 2.1.13

Detailed paths

Introduced through: golang@1.8-rc-stretch › apt@1.4~beta3
Introduced through: golang@1.8-rc-stretch › apt/libapt-pkg5.0@1.4~beta3

NVD Description

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

Remediation

Upgrade Debian:unstable apt to version 2.1.13 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Insufficiently Protected Credentials

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Remediation

Upgrade Debian:unstable curl to version 7.83.0-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

medium severity

Information Exposure

Vulnerable module: nettle/libhogweed4
Introduced through: nettle/libhogweed4@3.3-1 and nettle/libnettle6@3.3-1
Fixed in: 3.4.1~rc1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nettle/libhogweed4@3.3-1
Introduced through: golang@1.8-rc-stretch › nettle/libnettle6@3.3-1

NVD Description

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

Remediation

Upgrade Debian:unstable nettle to version 3.4.1~rc1-1 or higher.

References

Information Exposure vulnerability report

medium severity

Information Exposure

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.6.5-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

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

Remediation

Upgrade Debian:unstable gnutls28 to version 3.6.5-2 or higher.

References

Information Exposure vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.5.19-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found. An attacker could use a combination of "Just in Time" Prime+probe attack in combination with Lucky-13 attack to recover plain text using crafted packets.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.5.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Improper Input Validation

Vulnerable module: apt
Introduced through: apt@1.4~beta3 and apt/libapt-pkg5.0@1.4~beta3
Fixed in: 2.1.2

Detailed paths

Introduced through: golang@1.8-rc-stretch › apt@1.4~beta3
Introduced through: golang@1.8-rc-stretch › apt/libapt-pkg5.0@1.4~beta3

NVD Description

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

Remediation

Upgrade Debian:unstable apt to version 2.1.2 or higher.

References

Improper Input Validation vulnerability report

medium severity

Use After Free

Vulnerable module: bash
Introduced through: bash@4.4-2
Fixed in: 4.4-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › bash@4.4-2

NVD Description

popd in bash might allow local users to bypass the restricted shell and cause a use-after-free via a crafted address.

Remediation

Upgrade Debian:unstable bash to version 4.4-3 or higher.

References

Use After Free vulnerability report

medium severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-3 or higher.

References

Improper Input Validation vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The function coff_set_alignment_hook in coffcode.h in Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, has a memory leak vulnerability which can cause memory exhaustion in objdump via a crafted PE file. Additional validation in dump_relocs_in_section in objdump.c can resolve this.

Remediation

Upgrade Debian:unstable binutils to version 2.28-5 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-6 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29.1-2 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

readelf in GNU Binutils 2.28 writes to illegal addresses while processing corrupt input files containing symbol-difference relocations, leading to a heap-based buffer overflow.

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29-10 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30-4 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29-10 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Use After Free

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

readelf in GNU Binutils 2.28 has a use-after-free (specifically read-after-free) error while processing multiple, relocated sections in an MSP430 binary. This is caused by mishandling of an invalid symbol index, and mishandling of state across invocations.

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

Use After Free vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: coreutils
Introduced through: coreutils@8.26-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › coreutils@8.26-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

A flaw was found in the GNU coreutils "split" program. A heap overflow with user-controlled data of multiple hundred bytes in length could occur in the line_bytes_split() function, potentially leading to an application crash and denial of service.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

Out-of-bounds Write vulnerability report

medium severity

Improper Authentication

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-7 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Input Validation

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream elfutils package and not the elfutils package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

elflint.c in elfutils 0.168 does not validate the number of sections and the number of segments, which allows remote attackers to cause a denial of service (memory consumption) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Improper Input Validation

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

elf_compress.c in elfutils 0.168 does not validate the zlib compression factor, which allows remote attackers to cause a denial of service (memory consumption) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Improper Input Validation vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

An invalid memory address dereference was discovered in dwfl_segment_report_module.c in libdwfl in elfutils through v0.174. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by consider_notes.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The check_symtab_shndx function in elflint.c in elfutils 0.168 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The check_sysv_hash function in elflint.c in elfutils 0.168 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The ebl_object_note_type_name function in eblobjnotetypename.c in elfutils 0.168 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The handle_gnu_hash function in readelf.c in elfutils 0.168 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.168-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The check_group function in elflint.c in elfutils 0.168 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.168-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

dwarf_getaranges in dwarf_getaranges.c in libdw in elfutils before 2018-08-18 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted file.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

In elfutils 0.175, there is a buffer over-read in the ebl_object_note function in eblobjnote.c in libebl. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted elf file, as demonstrated by eu-readelf.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.180-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

The libcpu component which is used by libasm of elfutils version 0.177 (git 47780c9e), suffers from denial-of-service vulnerability caused by application crashes due to out-of-bounds write (CWE-787), off-by-one error (CWE-193) and reachable assertion (CWE-617); to exploit the vulnerability, the attackers need to craft certain ELF files which bypass the missing bound checks.

Remediation

Upgrade Debian:unstable elfutils to version 0.180-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Link Following

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.38.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's $GIT_DIR/objects directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via --no-hardlinks). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the --recurse-submodules option. Git does not create symbolic links in the $GIT_DIR/objects directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the --local optimization when on a shared machine, either by passing the --no-local option to git clone or cloning from a URL that uses the file:// scheme. Alternatively, avoid cloning repositories from untrusted sources with --recurse-submodules or run git config --global protocol.file.allow user.

Remediation

Upgrade Debian:unstable git to version 1:2.38.1-1 or higher.

References

Link Following vulnerability report

medium severity

Link Following

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.39.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253.

A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with --recurse-submodules. Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs.

Remediation

Upgrade Debian:unstable git to version 1:2.39.2-1 or higher.

References

Link Following vulnerability report

medium severity

Deserialization of Untrusted Data

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.74.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

A flaw was found in GLib. GVariant deserialization is vulnerable to an exponential blowup issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Deserialization of Untrusted Data vulnerability report

medium severity

Information Exposure

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.64.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

A flaw was found in glib before version 2.63.6. Due to random charset alias, pkexec can leak content from files owned by privileged users to unprivileged ones under the right condition.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.64.0-1 or higher.

References

Information Exposure vulnerability report

medium severity

Resource Exhaustion

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.74.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

A flaw was found in GLib. GVariant deserialization is vulnerable to a slowdown issue where a crafted GVariant can cause excessive processing, leading to denial of service.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.74.4-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid multi-byte input sequences in IBM1364, IBM1371, IBM1388, IBM1390, and IBM1399 encodings, fails to advance the input state, which could lead to an infinite loop in applications, resulting in a denial of service, a different vulnerability from CVE-2016-10228.

Remediation

Upgrade Debian:unstable glibc to version 2.31-5 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.30-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.30-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Use After Free

Vulnerable module: icu/libicu57
Introduced through: icu/libicu57@57.1-5
Fixed in: 67.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › icu/libicu57@57.1-5

NVD Description

International Components for Unicode (ICU-20850) v66.1 was discovered to contain a use after free bug in the pkg_createWithAssemblyCode function in the file tools/pkgdata/pkgdata.cpp.

Remediation

Upgrade Debian:unstable icu to version 67.1-2 or higher.

References

Use After Free vulnerability report

medium severity

CVE-2023-51384

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:9.6p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

In ssh-agent in OpenSSH before 9.6, certain destination constraints can be incompletely applied. When destination constraints are specified during addition of PKCS#11-hosted private keys, these constraints are only applied to the first key, even if a PKCS#11 token returns multiple keys.

Remediation

Upgrade Debian:unstable openssh to version 1:9.6p1-1 or higher.

References

CVE-2023-51384 vulnerability report

medium severity

CVE-2024-0727

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.1.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

CVE-2024-0727 vulnerability report

medium severity

CVE-2024-22365

Vulnerable module: pam/libpam-modules
Introduced through: pam/libpam-modules@1.1.8-3.5, pam/libpam-modules-bin@1.1.8-3.5 and others
Fixed in: 1.5.3-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › pam/libpam-modules@1.1.8-3.5
Introduced through: golang@1.8-rc-stretch › pam/libpam-modules-bin@1.1.8-3.5
Introduced through: golang@1.8-rc-stretch › pam/libpam-runtime@1.1.8-3.5
Introduced through: golang@1.8-rc-stretch › pam/libpam0g@1.1.8-3.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.

Remediation

Upgrade Debian:unstable pam to version 1.5.3-4 or higher.

References

CVE-2024-22365 vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2
Fixed in: 2:8.39-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

The _pcre32_xclass function in pcre_xclass.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (invalid memory read) via a crafted file.

Remediation

Upgrade Debian:unstable pcre3 to version 2:8.39-3 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Improper Authentication

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.13+dfsg1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.

Remediation

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

Improper Authentication vulnerability report

medium severity

Buffer Overflow

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

Buffer Overflow vulnerability found in SQLite3 v.3.27.1 and before allows a local attacker to cause a denial of service via a crafted script.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-1 or higher.

References

Buffer Overflow vulnerability report

medium severity

CVE-2020-13631

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

CVE-2020-13631 vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Write

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy heap overflow because of misuse of transitive properties for constant propagation.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.3-1 or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Uncontrolled Recursion

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.34.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

A flaw was found in SQLite's SELECT query functionality (src/select.c). This flaw allows an attacker who is capable of running SQL queries locally on the SQLite database to cause a denial of service or possible code execution by triggering a use-after-free. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.34.1-1 or higher.

References

Use After Free vulnerability report

medium severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.43.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.43.2-1 or higher.

References

Use After Free vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 247.3-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessive Size Value (involving strdupa and alloca for a pathname controlled by a local attacker) that results in an operating system crash.

Remediation

Upgrade Debian:unstable systemd to version 247.3-6 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

CVE-2022-4415

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 252.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.

Remediation

Upgrade Debian:unstable systemd to version 252.4-1 or higher.

References

CVE-2022-4415 vulnerability report

medium severity

Off-by-one Error

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 251.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.

Remediation

Upgrade Debian:unstable systemd to version 251.3-1 or higher.

References

Off-by-one Error vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 240-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the stack pointer to jump over the stack guard pages into an unmapped memory region and trigger a denial of service (systemd PID1 crash and kernel panic).

Remediation

Upgrade Debian:unstable systemd to version 240-6 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Resource Exhaustion

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 252-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.

Remediation

Upgrade Debian:unstable systemd to version 252-1 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Uncontrolled Recursion

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 250.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

A flaw was found in systemd. An uncontrolled recursion in systemd-tmpfiles may lead to a denial of service at boot time when too many nested directories are created in /tmp.

Remediation

Upgrade Debian:unstable systemd to version 250.2-1 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Files or Directories Accessible to External Parties

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.37.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows a local user on a vulnerable system to unmount other users' filesystems that are either world-writable themselves (like /tmp) or mounted in a world-writable directory. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

Files or Directories Accessible to External Parties vulnerability report

medium severity

Files or Directories Accessible to External Parties

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.37.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

A logic error was found in the libmount library of util-linux in the function that allows an unprivileged user to unmount a FUSE filesystem. This flaw allows an unprivileged local attacker to unmount FUSE filesystems that belong to certain other users who have a UID that is a prefix of the UID of the attacker in its string form. An attacker may use this flaw to cause a denial of service to applications that use the affected filesystems.

Remediation

Upgrade Debian:unstable util-linux to version 2.37.3-1 or higher.

References

Files or Directories Accessible to External Parties vulnerability report

medium severity

CVE-2022-27779

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without Public Suffix Listawareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

CVE-2022-27779 vulnerability report

medium severity

Improper Certificate Validation

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.6.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl inadvertently kept the SSL session ID for connections in its cache even when the verify status (OCSP stapling) test failed. A subsequent transfer to the same hostname could then succeed if the session ID cache was still fresh, which then skipped the verify status check.

Remediation

Upgrade Debian:unstable curl to version 8.6.0-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Information Exposure

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.74.0-1.2

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP requests, and therefore risks leaking sensitive data to the server that is the target of the second HTTP request.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1.2 or higher.

References

Information Exposure vulnerability report

medium severity

Missing Encryption of Sensitive Data

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.5.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When saving HSTS data to an excessively long file name, curl could end up removing all contents, making subsequent requests using that file unaware of the HSTS status they should otherwise use.

Remediation

Upgrade Debian:unstable curl to version 8.5.0-1 or higher.

References

Missing Encryption of Sensitive Data vulnerability report

medium severity

Link Following

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.66.7-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.7-2 or higher.

References

Link Following vulnerability report

medium severity

Improper Input Validation

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

Improper Input Validation vulnerability report

medium severity

Incorrect Calculation of Buffer Size

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.37-15

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

An integer overflow was found in the __vsyslog_internal function of the glibc library. This function is called by the syslog and vsyslog functions. This issue occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior. This issue affects glibc 2.37 and newer.

Remediation

Upgrade Debian:unstable glibc to version 2.37-15 or higher.

References

Incorrect Calculation of Buffer Size vulnerability report

medium severity

Incorrect Authorization

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:7.9p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

In OpenSSH 7.9, scp.c in the scp client allows remote SSH servers to bypass intended access restrictions via the filename of . or an empty filename. The impact is modifying the permissions of the target directory on the client side.

Remediation

Upgrade Debian:unstable openssh to version 1:7.9p1-5 or higher.

References

Incorrect Authorization vulnerability report

medium severity

Race Condition

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:7.7p1-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

Remediation

Upgrade Debian:unstable openssh to version 1:7.7p1-4 or higher.

References

Race Condition vulnerability report

medium severity

Excessive Iteration

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.10-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Excessive Iteration vulnerability report

medium severity

Improper Authentication

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.10-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Improper Authentication vulnerability report

medium severity

Improper Certificate Validation

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.

As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.

Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.

Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Certificate Validation

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.

Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.

Policy processing is disabled by default but can be enabled by passing the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Debian:unstable openssl to version 3.0.9-1 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Check for Unusual or Exceptional Conditions

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.12-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.12-2 or higher.

References

Improper Check for Unusual or Exceptional Conditions vulnerability report

medium severity

Inefficient Regular Expression Complexity

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.10-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Checking excessively long DH keys or parameters may be very slow.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Debian:unstable openssl to version 3.0.10-1 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

medium severity

Out-of-Bounds

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0g-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has been present since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0g-1 or higher.

References

Out-of-Bounds vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).

Remediation

Upgrade Debian:unstable openssl to version 3.0.5-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Use of Insufficiently Random Values

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

Use of Insufficiently Random Values vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: p11-kit/libp11-kit0
Introduced through: p11-kit/libp11-kit0@0.23.3-2
Fixed in: 0.23.22-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › p11-kit/libp11-kit0@0.23.3-2

NVD Description

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

Remediation

Upgrade Debian:unstable p11-kit to version 0.23.22-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Integer Overflow or Wraparound

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2
Fixed in: 2:8.39-13

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.

Remediation

Upgrade Debian:unstable pcre3 to version 2:8.39-13 or higher.

References

Integer Overflow or Wraparound vulnerability report

medium severity

Improper Handling of Exceptional Conditions

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

Improper Handling of Exceptional Conditions vulnerability report

medium severity

Out-of-bounds Read

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.0.8-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Remediation

Upgrade Debian:unstable openssl to version 3.0.8-1 or higher.

References

Out-of-bounds Read vulnerability report

medium severity

Reachable Assertion

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The iconv function in the GNU C Library (aka glibc or libc6) 2.30 to 2.32, when converting UCS4 text containing an irreversible character, fails an assertion in the code path and aborts the program, potentially resulting in a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-7 or higher.

References

Reachable Assertion vulnerability report

medium severity

NULL Pointer Dereference

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.16.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

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

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Information Exposure

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2
Fixed in: 1.8.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

Remediation

Upgrade Debian:unstable libgcrypt20 to version 1.8.3-1 or higher.

References

Information Exposure vulnerability report

medium severity

CVE-2019-1547

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

CVE-2019-1547 vulnerability report

medium severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1~~pre9-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

Remediation

Upgrade Debian:unstable openssl to version 1.1.1~~pre9-1 or higher.

References

Information Exposure vulnerability report

medium severity

Race Condition

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.4-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

A race condition was found in util-linux before 2.32.1 in the way su handled the management of child processes. A local authenticated attacker could use this flaw to kill other processes with root privileges under specific conditions.

Remediation

Upgrade Debian:unstable shadow to version 1:4.4-4 or higher.

References

Race Condition vulnerability report

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: tar
Introduced through: tar@1.29b-1.1
Fixed in: 1.30+dfsg-3.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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

Remediation

Upgrade Debian:unstable tar to version 1.30+dfsg-3.1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

medium severity

Use After Free

Vulnerable module: iproute2
Introduced through: iproute2@4.9.0-1
Fixed in: 5.2.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › iproute2@4.9.0-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream iproute2 package and not the iproute2 package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

iproute2 before 5.1.0 has a use-after-free in get_netnsid_from_name in ip/ipnetns.c. NOTE: security relevance may be limited to certain uses of setuid that, although not a default, are sometimes a configuration option offered to end users. Even when setuid is used, other factors (such as C library configuration) may block exploitability.

Remediation

Upgrade Debian:unstable iproute2 to version 5.2.0-1 or higher.

References

Use After Free vulnerability report

medium severity

CVE-2019-15718

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 242-7

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings.

Remediation

Upgrade Debian:unstable systemd to version 242-7 or higher.

References

CVE-2019-15718 vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.84.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A malicious server can serve excessive amounts of Set-Cookie: headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on foo.example.com can set cookies that also would match for bar.example.com, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

Remediation

Upgrade Debian:unstable curl to version 7.84.0-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Cleartext Transmission of Sensitive Information

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.83.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is provided in theURL. This mechanism could be bypassed if the host name in the given URL used atrailing dot while not using one when it built the HSTS cache. Or the otherway around - by having the trailing dot in the HSTS cache and not using thetrailing dot in the URL.

Remediation

Upgrade Debian:unstable curl to version 7.83.1-1 or higher.

References

Cleartext Transmission of Sensitive Information vulnerability report

medium severity

Information Exposure

Vulnerable module: subversion
Introduced through: subversion@1.9.5-1 and subversion/libsvn1@1.9.5-1
Fixed in: 1.14.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › subversion@1.9.5-1
Introduced through: golang@1.8-rc-stretch › subversion/libsvn1@1.9.5-1

NVD Description

Apache Subversion SVN authz protected copyfrom paths regression Subversion servers reveal 'copyfrom' paths that should be hidden according to configured path-based authorization (authz) rules. When a node has been copied from a protected location, users with access to the copy can see the 'copyfrom' path of the original. This also reveals the fact that the node was copied. Only the 'copyfrom' path is revealed; not its contents. Both httpd and svnserve servers are vulnerable.

Remediation

Upgrade Debian:unstable subversion to version 1.14.2-1 or higher.

References

Information Exposure vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.28-4 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Directory Traversal

Vulnerable module: dpkg
Introduced through: dpkg@1.18.18 and dpkg/libdpkg-perl@1.18.18
Fixed in: 1.18.24

Detailed paths

Introduced through: golang@1.8-rc-stretch › dpkg@1.18.18
Introduced through: golang@1.8-rc-stretch › dpkg/libdpkg-perl@1.18.18

NVD Description

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.

Remediation

Upgrade Debian:unstable dpkg to version 1.18.24 or higher.

References

Directory Traversal vulnerability report

low severity

Double Free

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

libelf/elf_end.c in elfutils 0.173 allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspecified other impact because it tries to decompress twice.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Double Free vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.58.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference.

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.0-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.25-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.25-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.27-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.27-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Double Free

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.15.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

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.

Remediation

Upgrade Debian:unstable krb5 to version 1.15.2-1 or higher.

References

Double Free vulnerability report

low severity

Out-of-Bounds

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.15.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

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.

Remediation

Upgrade Debian:unstable krb5 to version 1.15.2-2 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.36.0-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

In Perl 5.34.0, function S_find_uninit_var in sv.c has a stack-based crash that can lead to remote code execution or local privilege escalation.

Remediation

Upgrade Debian:unstable perl to version 5.36.0-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Use After Free

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.32.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.32.0-1 or higher.

References

Use After Free vulnerability report

low severity

Improper Certificate Validation

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 244-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent)

Remediation

Upgrade Debian:unstable systemd to version 244-1 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Improper Input Validation

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 234-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. "0day"), running the service in question with root privileges rather than the user intended.

Remediation

Upgrade Debian:unstable systemd to version 234-1 or higher.

References

Improper Input Validation vulnerability report

low severity

CVE-2005-2541

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Remediation

There is no fixed version for Debian:unstable tar.

References

CVE-2005-2541 vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: mercurial
Introduced through: mercurial@4.0-1 and mercurial/mercurial-common@4.0-1
Fixed in: 4.7.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › mercurial@4.0-1
Introduced through: golang@1.8-rc-stretch › mercurial/mercurial-common@4.0-1

NVD Description

cext/manifest.c in Mercurial before 4.7.2 has an out-of-bounds read during parsing of a malformed manifest entry.

Remediation

Upgrade Debian:unstable mercurial to version 4.7.2-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2020-19726

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in binutils libbfd.c 2.36 relating to the auxiliary symbol data allows attackers to read or write to system memory or cause a denial of service.

Remediation

Upgrade Debian:unstable binutils to version 2.37-3 or higher.

References

CVE-2020-19726 vulnerability report

low severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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).

Remediation

There is no fixed version for Debian:unstable git.

References

Improper Input Validation vulnerability report

low severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

low severity

Improper Input Validation

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Improper Input Validation vulnerability report

low severity

CVE-2019-1010023

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable glibc.

References

CVE-2019-1010023 vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.2+20200912-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Remediation

Upgrade Debian:unstable ncurses to version 6.2+20200912-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Underflow

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

Remediation

Upgrade Debian:unstable glibc to version 2.31-2 or higher.

References

Integer Underflow vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: libssh2/libssh2-1
Introduced through: libssh2/libssh2-1@1.7.0-1
Fixed in: 1.9.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libssh2/libssh2-1@1.7.0-1

NVD Description

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.

Remediation

Upgrade Debian:unstable libssh2 to version 1.9.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: lz4/liblz4-1
Introduced through: lz4/liblz4-1@0.0~r131-2
Fixed in: 1.9.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › lz4/liblz4-1@0.0~r131-2

NVD Description

LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize), affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data corruption.) NOTE: the vendor states "only a few specific / uncommon usages of the API are at risk."

Remediation

Upgrade Debian:unstable lz4 to version 1.9.2-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Improper Certificate Validation

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others
Fixed in: 5.38.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.

Remediation

Upgrade Debian:unstable perl to version 5.38.2-2 or higher.

References

Improper Certificate Validation vulnerability report

low severity

Improper Check for Dropped Privileges

Vulnerable module: bash
Introduced through: bash@4.4-2
Fixed in: 5.1~rc1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › bash@4.4-2

NVD Description

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.

Remediation

Upgrade Debian:unstable bash to version 5.1~rc1-2 or higher.

References

Improper Check for Dropped Privileges vulnerability report

low severity

CVE-2022-47695

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function bfd_mach_o_get_synthetic_symtab in match-o.c.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-2 or higher.

References

CVE-2022-47695 vulnerability report

low severity

CVE-2022-47696

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function compare_symbols.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-2 or higher.

References

CVE-2022-47696 vulnerability report

low severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Incorrect Type Conversion or Cast

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Incorrect Type Conversion or Cast vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable binutils.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was found in binutils readelf 2.35 program. An attacker who is able to convince a victim using readelf to read a crafted file could trigger a stack buffer overflow, out-of-bounds write of arbitrary data supplied by the attacker. The highest impact of this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Debian:unstable binutils to version 2.35.2-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221224-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out of bound reads which may cause a denial of service or other unspecified impacts.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221224-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37.50.20220106-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

stab_xcoff_builtin_type in stabs.c in GNU Binutils through 2.37 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. NOTE: this issue exists because of an incorrect fix for CVE-2018-12699.

Remediation

Upgrade Debian:unstable binutils to version 2.37.50.20220106-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Heap based buffer overflow in binutils-gdb/bfd/libbfd.c in bfd_getl64.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Heap buffer overflow vulnerability in binutils readelf before 2.40 via function display_debug_section in file readelf.c.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Heap buffer overflow vulnerability in binutils readelf before 2.40 via function find_section_in_set in file readelf.c.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.66.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

GNOME GLib before 2.65.3 has an integer overflow, that might lead to an out-of-bounds write, in g_option_group_add_entries. NOTE: the vendor's position is "Realistically this is not a security issue. The standard pattern is for callers to provide a static list of option entries in a fixed number of calls to g_option_group_add_entries()." The researcher states that this pattern is undocumented

Remediation

Upgrade Debian:unstable glib2.0 to version 2.66.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Improper Resource Shutdown or Release

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

Improper Resource Shutdown or Release vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.27-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

Upgrade Debian:unstable glibc to version 2.27-4 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: inetutils/inetutils-ping
Introduced through: inetutils/inetutils-ping@2:1.9.4-2+b1
Fixed in: 2:1.9.4-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › inetutils/inetutils-ping@2:1.9.4-2+b1

NVD Description

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.

Remediation

Upgrade Debian:unstable inetutils to version 2:1.9.4-11 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:8.1p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH 7.7 through 7.9 and 8.x before 8.1, when compiled with an experimental key type, has a pre-authentication integer overflow if a client or server is configured to use a crafted XMSS key. This leads to memory corruption and local code execution because of an error in the XMSS key parsing algorithm. NOTE: the XMSS implementation is considered experimental in all released OpenSSH versions, and there is no supported way to enable it when building portable OpenSSH.

Remediation

Upgrade Debian:unstable openssh to version 1:8.1p1-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

OS Command Injection

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Remediation

There is no fixed version for Debian:unstable openssh.

References

OS Command Injection vulnerability report

low severity

Out-of-Bounds

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.

Remediation

There is no fixed version for Debian:unstable pcre3.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.

Remediation

There is no fixed version for Debian:unstable pcre3.

References

Out-of-Bounds vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).

Remediation

There is no fixed version for Debian:unstable shadow.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

CVE-2018-6954

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 238-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd-tmpfiles in systemd through 237 mishandles symlinks present in non-terminal path components, which allows local users to obtain ownership of arbitrary files via vectors involving creation of a directory and a file under that directory, and later replacing that directory with a symlink. This occurs even if the fs.protected_symlinks sysctl is turned on.

Remediation

Upgrade Debian:unstable systemd to version 238-1 or higher.

References

CVE-2018-6954 vulnerability report

low severity

Link Following

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 237-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd-tmpfiles in systemd before 237 attempts to support ownership/permission changes on hardlinked files even if the fs.protected_hardlinks sysctl is turned off, which allows local users to bypass intended access restrictions via vectors involving a hard link to a file for which the user lacks write access, as demonstrated by changing the ownership of the /etc/passwd file.

Remediation

Upgrade Debian:unstable systemd to version 237-1 or higher.

References

Link Following vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

CVE-2018-12698

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

CVE-2018-12698 vulnerability report

low severity

Improper Initialization

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils before 2.34 has an uninitialized-heap vulnerability in function tic4x_print_cond (file opcodes/tic4x-dis.c) which could allow attackers to make an information leak.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

Improper Initialization vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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).

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37.90.20220207-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37.

Remediation

Upgrade Debian:unstable binutils to version 2.37.90.20220207-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37.90.20220207-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was discovered in GNU libiberty within demangle_path() in rust-demangle.c, as distributed in GNU Binutils version 2.36. A crafted symbol can cause stack memory to be exhausted leading to a crash.

Remediation

Upgrade Debian:unstable binutils to version 2.37.90.20220207-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

Exposure of Resource to Wrong Sphere

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option.

Remediation

There is no fixed version for Debian:unstable git.

References

Exposure of Resource to Wrong Sphere vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.17.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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.

Remediation

Upgrade Debian:unstable git to version 1:2.17.1-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Use of Incorrectly-Resolved Name or Reference

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2
Fixed in: 2.58.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c, related to utf8_str().

Remediation

Upgrade Debian:unstable glib2.0 to version 2.58.0-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2021-43396

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.32-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

In iconvdata/iso-2022-jp-3.c in the GNU C Library (aka glibc) 2.34, remote attackers can force iconv() to emit a spurious '\0' character via crafted ISO-2022-JP-3 data that is accompanied by an internal state reset. This may affect data integrity in certain iconv() use cases. NOTE: the vendor states "the bug cannot be invoked through user input and requires iconv to be invoked with a NULL inbuf, which ought to require a separate application bug to do so unintentionally. Hence there's no security impact to the bug.

Remediation

Upgrade Debian:unstable glibc to version 2.32-5 or higher.

References

CVE-2021-43396 vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8 and glibc/multiarch-support@2.24-8
Fixed in: 2.24-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

res_query in libresolv in glibc before 2.25 allows remote attackers to cause a denial of service (NULL pointer dereference and process crash).

Remediation

Upgrade Debian:unstable glibc to version 2.24-9 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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

Remediation

There is no fixed version for Debian:unstable glibc.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Uncontrolled Recursion vulnerability report

low severity

Key Management Errors

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2
Fixed in: 2.2.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid certifications that occurred only with access to a signing subkey.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.7-1 or higher.

References

Key Management Errors vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2
Fixed in: 2.2.19-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

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.

Remediation

Upgrade Debian:unstable gnupg2 to version 2.2.19-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Integer Overflow or Wraparound

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable krb5.

References

Integer Overflow or Wraparound vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable libgcrypt20.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Improper Input Validation

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.31.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

nghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.31.1-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Cryptographic Issues

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

Remediation

There is no fixed version for Debian:unstable openldap.

References

Cryptographic Issues vulnerability report

low severity

CVE-2019-13565

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.48+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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.

Remediation

Upgrade Debian:unstable openldap to version 2.4.48+dfsg-1 or higher.

References

CVE-2019-13565 vulnerability report

low severity

Out-of-Bounds

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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.

Remediation

There is no fixed version for Debian:unstable openldap.

References

Out-of-Bounds vulnerability report

low severity

Improper Input Validation

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:8.3p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

The scp client in OpenSSH 8.2 incorrectly sends duplicate responses to the server upon a utimes system call failure, which allows a malicious unprivileged user on the remote server to overwrite arbitrary files in the client's download directory by creating a crafted subdirectory anywhere on the remote server. The victim must use the command scp -rp to download a file hierarchy containing, anywhere inside, this crafted subdirectory. NOTE: the vendor points out that "this attack can achieve no more than a hostile peer is already able to achieve within the scp protocol" and "utimes does not fail under normal circumstances.

Remediation

Upgrade Debian:unstable openssh to version 1:8.3p1-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Key Management Errors

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1-1 or higher.

References

Key Management Errors vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.

Remediation

There is no fixed version for Debian:unstable pcre3.

References

Out-of-bounds Read vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

Remediation

There is no fixed version for Debian:unstable pcre3.

References

Uncontrolled Recursion vulnerability report

low severity

Link Following

Vulnerable module: perl
Introduced through: perl@5.24.1~rc4-1, perl/libperl5.24@5.24.1~rc4-1 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › perl@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/libperl5.24@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-base@5.24.1~rc4-1
Introduced through: golang@1.8-rc-stretch › perl/perl-modules-5.24@5.24.1~rc4-1

NVD Description

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

Remediation

There is no fixed version for Debian:unstable perl.

References

Link Following vulnerability report

low severity

CVE-2019-19244

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.30.1+fossil191229-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

sqlite3Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.30.1+fossil191229-1 or higher.

References

CVE-2019-19244 vulnerability report

low severity

Improper Validation of Array Index

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.39.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.39.2-1 or higher.

References

Improper Validation of Array Index vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.20.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

SQLite 3.20.1 has a NULL pointer dereference in tableColumnList in shell.c because it fails to consider certain cases where sqlite3_step(pStmt)==SQLITE_ROW is false and a data structure is never initialized.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.20.1-2 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.36.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.36.0-2 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.27.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

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

Remediation

Upgrade Debian:unstable sqlite3 to version 3.27.2-2 or higher.

References

Out-of-bounds Read vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: tar
Introduced through: tar@1.29b-1.1
Fixed in: 1.32+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

Remediation

Upgrade Debian:unstable tar to version 1.32+dfsg-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1c-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1c-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: apr/libapr1
Introduced through: apr/libapr1@1.5.2-5
Fixed in: 1.6.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › apr/libapr1@1.5.2-5

NVD Description

When apr_time_exp*() or apr_os_exp_time*() functions are invoked with an invalid month field value in Apache Portable Runtime APR 1.6.2 and prior, out of bounds memory may be accessed in converting this value to an apr_time_exp_t value, potentially revealing the contents of a different static heap value or resulting in program termination, and may represent an information disclosure or denial of service vulnerability to applications which call these APR functions with unvalidated external input.

Remediation

Upgrade Debian:unstable apr to version 1.6.3-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An out of bounds flaw was found in GNU binutils objdump utility version 2.36. An attacker could use this flaw and pass a large section to avr_elf32_load_records_from_section() probably resulting in a crash or in some cases memory corruption. The highest threat from this vulnerability is to integrity as well as system availability.

Remediation

Upgrade Debian:unstable binutils to version 2.37-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221224-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An out-of-bounds read flaw was found in the parse_module function in bfd/vms-alpha.c in Binutils.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221224-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2023-51767

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH through 9.6, when common types of DRAM are used, might allow row hammer attacks (for authentication bypass) because the integer value of authenticated in mm_answer_authpassword does not resist flips of a single bit. NOTE: this is applicable to a certain threat model of attacker-victim co-location in which the attacker has user privileges.

Remediation

There is no fixed version for Debian:unstable openssh.

References

CVE-2023-51767 vulnerability report

low severity

Inappropriate Encoding for Output Context

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Inappropriate Encoding for Output Context vulnerability report

low severity

Improper Input Validation

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 246-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.

Remediation

Upgrade Debian:unstable systemd to version 246-2 or higher.

References

Improper Input Validation vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.34-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is an integer overflow leading to a SEGV in _bfd_dwarf2_find_nearest_line in dwarf2.c, as demonstrated by nm.

Remediation

Upgrade Debian:unstable binutils to version 2.34-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a NULL pointer dereference in work_stuff_copy_to_from when called from iterate_demangle_function.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37.50.20220121-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Heap/stack buffer overflow in the dlang_lname function in d-demangle.c in libiberty allows attackers to potentially cause a denial of service (segmentation fault and crash) via a crafted mangled symbol.

Remediation

Upgrade Debian:unstable binutils to version 2.37.50.20220121-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.

Remediation

There is no fixed version for Debian:unstable binutils.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.41-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A potential heap based buffer overflow was found in _bfd_elf_slurp_version_tables() in bfd/elf.c. This may lead to loss of availability.

Remediation

Upgrade Debian:unstable binutils to version 2.41-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.

Remediation

There is no fixed version for Debian:unstable binutils.

References

Out-of-bounds Write vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.34-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

find_abstract_instance in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32, allows remote attackers to cause a denial of service (infinite recursion and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.34-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

CVE-2016-3189

Vulnerable module: bzip2/libbz2-1.0
Introduced through: bzip2/libbz2-1.0@1.0.6-8
Fixed in: 1.0.6-8.1

Detailed paths

Introduced through: golang@1.8-rc-stretch › bzip2/libbz2-1.0@1.0.6-8

NVD Description

Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start of the block.

Remediation

Upgrade Debian:unstable bzip2 to version 1.0.6-8.1 or higher.

References

CVE-2016-3189 vulnerability report

low severity

Improper Input Validation

Vulnerable module: coreutils
Introduced through: coreutils@8.26-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › coreutils@8.26-1

NVD Description

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

Improper Input Validation vulnerability report

low severity

Improper Validation of Integrity Check Value

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

An attempted excessive memory allocation was discovered in the function read_long_names in elf_begin.c in libelf in elfutils 0.174. Remote attackers could leverage this vulnerability to cause a denial-of-service via crafted elf input, which leads to an out-of-memory exception. NOTE: The maintainers believe this is not a real issue, but instead a "warning caused by ASAN because the allocation is big. By setting ASAN_OPTIONS=allocator_may_return_null=1 and running the reproducer, nothing happens."

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Out-of-Bounds

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

An Invalid Memory Address Dereference exists in the function elf_end in libelf in elfutils through v0.174. Although eu-size is intended to support ar files inside ar files, handle_ar in size.c closes the outer ar file before handling all inner entries. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

A heap-based buffer over-read was discovered in the function read_srclines in dwarf_getsrclines.c in libdw in elfutils 0.175. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by eu-nm.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Link Following

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

There is an open race window when writing output in the following utilities in GNU binutils version 2.35 and earlier:ar, objcopy, strip, ranlib. When these utilities are run as a privileged user (presumably as part of a script updating binaries across different users), an unprivileged user can trick these utilities into getting ownership of arbitrary files through a symlink.

Remediation

Upgrade Debian:unstable binutils to version 2.37-3 or higher.

References

Link Following vulnerability report

low severity

XML External Entity (XXE) Injection

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.4.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue. NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE.

Remediation

Upgrade Debian:unstable expat to version 2.4.1-2 or higher.

References

XML External Entity (XXE) Injection vulnerability report

low severity

Access Restriction Bypass

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

sshd in OpenSSH 4 on Debian GNU/Linux, and the 20070303 OpenSSH snapshot, allows remote authenticated users to obtain access to arbitrary SELinux roles by appending a :/ (colon slash) sequence, followed by the role name, to the username.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Access Restriction Bypass vulnerability report

low severity

Access Restriction Bypass

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

Remediation

There is no fixed version for Debian:unstable shadow.

References

Access Restriction Bypass vulnerability report

low severity

Use of Uninitialized Resource

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

There's a flaw in binutils /opcodes/tic4x-dis.c. An attacker who is able to submit a crafted input file to be processed by binutils could cause usage of uninitialized memory. The highest threat is to application availability with a lower threat to data confidentiality. This flaw affects binutils versions prior to 2.34.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

Use of Uninitialized Resource vulnerability report

low severity

Authentication Bypass

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 249.4-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.

Remediation

Upgrade Debian:unstable systemd to version 249.4-2 or higher.

References

Authentication Bypass vulnerability report

low severity

Race Condition

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using alarm() and siglongjmp(). When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

Race Condition vulnerability report

low severity

Improper Data Handling

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

Remediation

Upgrade Debian:unstable glibc to version 2.28-1 or higher.

References

Improper Data Handling vulnerability report

low severity

Improper Input Validation

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

Remediation

Upgrade Debian:unstable glibc to version 2.31-3 or higher.

References

Improper Input Validation vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.25-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The glob function in glob.c in the GNU C Library (aka glibc or libc6) before 2.27, when invoked with GLOB_TILDE, could skip freeing allocated memory when processing the ~ operator with a long user name, potentially leading to a denial of service (memory leak).

Remediation

Upgrade Debian:unstable glibc to version 2.25-3 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

Information Exposure

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

CVE-2018-0733

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0h-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Because of an implementation bug the PA-RISC CRYPTO_memcmp function is effectively reduced to only comparing the least significant bit of each byte. This allows an attacker to forge messages that would be considered as authenticated in an amount of tries lower than that guaranteed by the security claims of the scheme. The module can only be compiled by the HP-UX assembler, so that only HP-UX PA-RISC targets are affected. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

CVE-2018-0733 vulnerability report

low severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0h-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). Note: The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n. Due to the low severity of this issue we are not issuing a new release of OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h when it becomes available. The fix is also available in commit e502cc86d in the OpenSSL git repository.

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-1 or higher.

References

Information Exposure vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.0h-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o).

Remediation

Upgrade Debian:unstable openssl to version 1.1.0h-3 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.28-6 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

There is no fixed version for Debian:unstable binutils.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Allocation of Resources Without Limits or Throttling

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

low severity

Divide By Zero

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Divide By Zero vulnerability report

low severity

Double Free

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A double free vulnerability exists in the Binary File Descriptor (BFD) (aka libbrd) in GNU Binutils 2.35 in the process_symbol_table, as demonstrated in readelf, via a crafted file.

Remediation

Upgrade Debian:unstable binutils to version 2.35-1 or higher.

References

Double Free vulnerability report

low severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.30.90.20180627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.30.90.20180627-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Improper Input Validation

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Incorrect Calculation of Buffer Size

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Incorrect Calculation of Buffer Size vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190813-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

apply_relocations in readelf.c in GNU Binutils 2.32 contains an integer overflow that allows attackers to trigger a write access violation (in byte_put_little_endian function in elfcomm.c) via an ELF file, as demonstrated by readelf.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190813-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a stack consumption vulnerability resulting from infinite recursion in the functions d_name(), d_encoding(), and d_local_name() in cp-demangle.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via an ELF file, as demonstrated by nm.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

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

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

read_formatted_entries in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (infinite loop) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a stack consumption vulnerability resulting from infinite recursion in the functions next_is_type_qual() and cplus_demangle_type() in cp-demangle.c. Remote attackers could leverage this vulnerability to cause a denial-of-service via an ELF file, as demonstrated by nm.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function find_abstract_instance in dwarf2.c.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in GNU Binutils 2.34. It is a memory leak when process microblaze-dis.c. This one will consume memory on each insn disassembled.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

Memory Leak vulnerability report

low severity

Memory Leak

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200114-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A memory consumption issue in get_data function in binutils/nm.c in GNU nm before 2.34 allows attackers to cause a denial of service via crafted command.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200114-1 or higher.

References

Memory Leak vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

_bfd_dwarf2_cleanup_debug_info in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (memory leak) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The _bfd_generic_read_minisymbols function in syms.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31, has a memory leak via a crafted ELF file, leading to a denial of service (memory consumption), as demonstrated by nm.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Memory leak in decode_line_info in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (memory consumption) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A Null Pointer Dereference vulnerability exists in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35, in scan_unit_for_symbols, as demonstrated in addr2line, that can cause a denial of service via a crafted file.

Remediation

Upgrade Debian:unstable binutils to version 2.35-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A Null Pointer Dereference vulnerability exists in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35, in _bfd_elf_get_symbol_version_string, as demonstrated in nm-new, that can cause a denial of service via a crafted file.

Remediation

Upgrade Debian:unstable binutils to version 2.35-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

There's a flaw in binutils /bfd/pef.c. An attacker who is able to submit a crafted input file to be processed by the objdump program could cause a null pointer dereference. The greatest threat from this flaw is to application availability. This flaw affects binutils versions prior to 2.34.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

There's a flaw in bfd_pef_scan_start_address() of bfd/pef.c in binutils which could allow an attacker who is able to submit a crafted file to be processed by objdump to cause a NULL pointer dereference. The greatest threat of this flaw is to application availability. This flaw affects binutils versions prior to 2.34.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33.50.20200107-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

There's a flaw in bfd_pef_parse_function_stubs of bfd/pef.c in binutils in versions prior to 2.34 which could allow an attacker who is able to submit a crafted file to be processed by objdump to cause a NULL pointer dereference. The greatest threat of this flaw is to application availability.

Remediation

Upgrade Debian:unstable binutils to version 2.33.50.20200107-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An illegal memory access flaw was found in the binutils package. Parsing an ELF file containing corrupt symbol version information may result in a denial of service. This issue is the result of an incomplete fix for CVE-2020-16599.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-2 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The dump_section_as_bytes function in readelf in GNU Binutils 2.28 accesses a NULL pointer while reading section contents in a corrupt binary, leading to a program crash.

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils 2017-04-03 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash), related to the process_mips_specific function in readelf.c, via a crafted ELF file that triggers a large memory-allocation attempt.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the merge_strings function in merge.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. There is a NULL pointer dereference in _bfd_add_merge_section when attempting to merge sections with large alignments. A specially crafted ELF allows remote attackers to cause a denial of service, as demonstrated by ld.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The coff_slurp_reloc_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 (NULL pointer dereference and application crash) via a crafted COFF based file.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

scan_unit_for_symbols in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A NULL pointer dereference was discovered in elf_link_add_object_symbols in elflink.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31.1. This occurs for a crafted ET_DYN with no program headers. A specially crafted ELF file allows remote attackers to cause a denial of service, as demonstrated by ld.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in elf_link_input_bfd in elflink.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. There is a NULL pointer dereference in elf_link_input_bfd when used for finding STT_TLS symbols without any TLS section. A specially crafted ELF allows remote attackers to cause a denial of service, as demonstrated by ld.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, does not validate the DW_AT_name data type, which allows remote attackers to cause a denial of service (bfd_hash_hash NULL pointer dereference, or out-of-bounds access, and application crash) via a crafted ELF file, related to scan_unit_for_symbols and parse_comp_unit.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

read_formatted_entries in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, does not properly validate the format count, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted ELF file, related to concat_filename.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

Null pointer dereference vulnerability in Binutils readelf 2.38.50 via function read_and_display_attr_value in file dwarf.c.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was found in GNU Binutils 2.35.1, where there is a heap-based buffer overflow in _bfd_elf_slurp_secondary_reloc_section in elf.c due to the number of symbols not calculated correctly. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable binutils to version 2.37-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

objdump in GNU Binutils 2.28 is vulnerable to multiple heap-based buffer over-reads (of size 1 and size 8) while handling corrupt STABS enum type strings in a crafted object file, leading to program crash.

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. An invalid memory access exists in _bfd_stab_section_find_nearest_line in syms.c. Attackers could leverage this vulnerability to cause a denial of service (application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The d_print_comp function in cp-demangle.c in libiberty allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted binary, which triggers infinite recursion and a buffer overflow, related to a node having "itself as ancestor more than once."

Remediation

Upgrade Debian:unstable binutils to version 2.28-3 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. An invalid memory access exists in bfd_zalloc in opncls.c. Attackers could leverage this vulnerability to cause a denial of service (application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-Bounds

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. An invalid memory address dereference was discovered in read_reloc in reloc.c. The vulnerability causes a segmentation fault and application crash, which leads to denial of service, as demonstrated by objdump, because of missing _bfd_clear_contents bounds checking.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-Bounds vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A Denial of Service vulnerability exists in the Binary File Descriptor (BFD) in GNU Binutils 2.35 due to an invalid read in process_symbol_table, as demonstrated in readeif.

Remediation

Upgrade Debian:unstable binutils to version 2.35-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. It is an out-of-bounds read leading to a SEGV in bfd_getl32 in libbfd.c, when called from pex64_get_runtime_function in pei-x86_64.c.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The print_symbol_for_build_attribute function in readelf.c in GNU Binutils 2017-04-12 allows remote attackers to cause a denial of service (invalid read and SEGV) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils 2.28 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file, related to the byte_get_little_endian function in elfcomm.c, the get_unwind_section_word function in readelf.c, and ARM unwind information that contains invalid word offsets.

Remediation

Upgrade Debian:unstable binutils to version 2.28-6 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The _bfd_elf_parse_attributes function in elf-attrs.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 (_bfd_elf_attr_strdup heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils 2.28 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file, related to MIPS GOT mishandling in the process_mips_specific function in readelf.c.

Remediation

Upgrade Debian:unstable binutils to version 2.28-6 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

elf.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not validate sizes of core notes, which allows remote attackers to cause a denial of service (bfd_getl32 heap-based buffer over-read and application crash) via a crafted object file, related to elfcore_grok_netbsd_procinfo, elfcore_grok_openbsd_procinfo, and elfcore_grok_nto_status.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. a heap-based buffer over-read in bfd_getl32 in libbfd.c allows an attacker to cause a denial of service through a crafted PE file. This vulnerability can be triggered by the executable objdump.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A heap-based buffer over-read issue was discovered in the function sec_merge_hash_lookup in merge.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31, because _bfd_add_merge_section mishandles section merges when size is not a multiple of entsize. A specially crafted ELF allows remote attackers to cause a denial of service, as demonstrated by ld.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The read_section function in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (parse_comp_unit heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29-10 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

bfd_get_debug_link_info_1 in opncls.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 (heap-based buffer over-read and application crash) via a crafted ELF file, related to bfd_getl32.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29.90.20180122-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

decode_line_info in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, mishandles a length calculation, which allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted ELF file, related to read_1_byte.

Remediation

Upgrade Debian:unstable binutils to version 2.29.90.20180122-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.29-9

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The decode_line_info function in dwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (read_1_byte heap-based buffer over-read and application crash) via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.29-9 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.32. There is a heap-based buffer over-read in _bfd_doprnt in bfd.c because elf_object_p in elfcode.h mishandles an e_shstrndx section of type SHT_GROUP by omitting a trailing '\0' character.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

In GNU Binutils before 2.40, there is a heap-buffer-overflow in the error function bfd_getl32 when called from the strip_main function in strip-new via a crafted file.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-2 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.

Remediation

There is no fixed version for Debian:unstable binutils.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

load_specific_debug_section in objdump.c in GNU Binutils through 2.31.1 contains an integer overflow vulnerability that can trigger a heap-based buffer overflow via a crafted section size.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.33-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.32. simple_object_elf_match in simple-object-elf.c does not check for a zero shstrndx value, leading to an integer overflow and resultant heap-based buffer overflow.

Remediation

Upgrade Debian:unstable binutils to version 2.33-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Reachable Assertion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.38.50.20220627-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in Binutils readelf 2.38.50, reachable assertion failure in function display_debug_names allows attackers to cause a denial of service.

Remediation

Upgrade Debian:unstable binutils to version 2.38.50.20220627-1 or higher.

References

Reachable Assertion vulnerability report

low severity

Resource Exhaustion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. There is a stack consumption problem caused by the cplus_demangle_type function making recursive calls to itself in certain scenarios involving many 'P' characters.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Resource Exhaustion vulnerability report

low severity

Resource Exhaustion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.40-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.

Remediation

Upgrade Debian:unstable binutils to version 2.40-2 or higher.

References

Resource Exhaustion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37.90.20220207-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

GCC v12.0 was discovered to contain an uncontrolled recursion via the component libiberty/rust-demangle.c. This vulnerability allows attackers to cause a Denial of Service (DoS) by consuming excessive CPU and memory resources.

Remediation

Upgrade Debian:unstable binutils to version 2.37.90.20220207-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.32. It is a stack consumption issue in d_count_templates_scopes in cp-demangle.c after many recursive calls.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there is a stack consumption problem caused by recursive stack frames: cplus_demangle_type, d_bare_function_type, d_function_type.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.29 and 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_nested_args, demangle_args, do_arg, and do_type.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Uncontrolled Recursion vulnerability report

low severity

Uncontrolled Recursion

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.

Remediation

There is no fixed version for Debian:unstable binutils.

References

Uncontrolled Recursion vulnerability report

low severity

Use After Free

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.35-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A use after free issue exists in the Binary File Descriptor (BFD) library (aka libbfd) in GNU Binutils 2.34 in bfd_hash_lookup, as demonstrated in nm-new, that can cause a denial of service via a crafted file.

Remediation

Upgrade Debian:unstable binutils to version 2.35-1 or higher.

References

Use After Free vulnerability report

low severity

Use After Free

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.32.51.20190707-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

In GNU Binutils 2.31.1, there is a use-after-free in the error function in elfcomm.c when called from the process_archive function in readelf.c via a crafted ELF file.

Remediation

Upgrade Debian:unstable binutils to version 2.32.51.20190707-1 or higher.

References

Use After Free vulnerability report

low severity

Use of Uninitialized Resource

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was found in Binutils. The field the_bfd of asymbolstruct is uninitialized in the bfd_mach_o_get_synthetic_symtab function, which may lead to an application crash and local denial of service.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-1 or higher.

References

Use of Uninitialized Resource vulnerability report

low severity

Use of Uninitialized Resource

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221208-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was found in Binutils. A logic fail in the bfd_init_section_decompress_status function may lead to the use of an uninitialized variable that can cause a crash and local denial of service.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221208-1 or higher.

References

Use of Uninitialized Resource vulnerability report

low severity

Use of Uninitialized Resource

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.39.50.20221224-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

A flaw was found in Binutils. The use of an uninitialized field in the struct module *module may lead to application crash and local denial of service.

Remediation

Upgrade Debian:unstable binutils to version 2.39.50.20221224-1 or higher.

References

Use of Uninitialized Resource vulnerability report

low severity

Divide By Zero

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

Divide-by-zero vulnerabilities in the function arlib_add_symbols() in arlib.c in elfutils 0.174 allow remote attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by eu-ranlib, because a zero sh_entsize is mishandled.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Divide By Zero vulnerability report

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.185-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

In elfutils 0.183, an infinite loop was found in the function handle_symtab in readelf.c .Which allows attackers to cause a denial of service (infinite loop) via crafted file.

Remediation

Upgrade Debian:unstable elfutils to version 0.185-2 or higher.

References

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

An issue was discovered in elfutils 0.175. A segmentation fault can occur in the function elf64_xlatetom in libelf/elf32_xlatetom.c, due to dwfl_segment_report_module not checking whether the dyn data read from a core file is truncated. A crafted input can cause a program crash, leading to denial-of-service, as demonstrated by eu-stack.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.175-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

libdw in elfutils 0.173 checks the end of the attributes list incorrectly in dwarf_getabbrev in dwarf_getabbrev.c and dwarf_hasattr in dwarf_hasattr.c, leading to a heap-based buffer over-read and an application crash.

Remediation

Upgrade Debian:unstable elfutils to version 0.175-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

In elfutils 0.175, a heap-based buffer over-read was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf. A crafted ELF input can cause a segmentation fault leading to denial of service (program crash) because ebl_core_note does not reject malformed core file notes.

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2
Fixed in: 0.176-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

In elfutils 0.175, a negative-sized memcpy is attempted in elf_cvt_note in libelf/note_xlate.h because of an incorrect overflow check. Crafted elf input causes a segmentation fault, leading to denial of service (program crash).

Remediation

Upgrade Debian:unstable elfutils to version 0.176-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.6.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.

Remediation

Upgrade Debian:unstable expat to version 2.6.0-1 or higher.

References

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') vulnerability report

low severity

Resource Exhaustion

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.16.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

Git through 2.14.2 mishandles layers of tree objects, which allows remote attackers to cause a denial of service (memory consumption) via a crafted repository, aka a Git bomb. This can also have an impact of disk consumption; however, an affected process typically would not survive its attempt to build the data structure in memory before writing to disk.

Remediation

Upgrade Debian:unstable git to version 1:2.16.1-1 or higher.

References

Resource Exhaustion vulnerability report

low severity

CVE-2019-7309

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.28-6

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

Remediation

Upgrade Debian:unstable glibc to version 2.28-6 or higher.

References

CVE-2019-7309 vulnerability report

low severity

CVE-2018-1000654

Vulnerable module: libtasn1-6
Introduced through: libtasn1-6@4.9-4
Fixed in: 4.14-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libtasn1-6@4.9-4

NVD Description

GNU Libtasn1-4.13 libtasn1-4.13 version libtasn1-4.13, libtasn1-4.12 contains a DoS, specifically CPU usage will reach 100% when running asn1Paser against the POC due to an issue in _asn1_expand_object_id(p_tree), after a long time, the program will be killed. This attack appears to be exploitable via parsing a crafted file.

Remediation

Upgrade Debian:unstable libtasn1-6 to version 4.14-2 or higher.

References

CVE-2018-1000654 vulnerability report

low severity

NULL Pointer Dereference

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20180210-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

In ncurses 6.1, there is a NULL pointer dereference at function _nc_parse_entry in parse_entry.c that will lead to a denial of service attack. The product proceeds to the dereference code path even after a "dubious character `*' in name or alias field" detection.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20180210-3 or higher.

References

NULL Pointer Dereference vulnerability report

low severity

Out-of-Bounds

Vulnerable module: pcre3/libpcre3
Introduced through: pcre3/libpcre3@2:8.39-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › pcre3/libpcre3@2:8.39-2

NVD Description

In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used

Remediation

There is no fixed version for Debian:unstable pcre3.

References

Out-of-Bounds vulnerability report

low severity

Improper Input Validation

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2
Fixed in: 3.20.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

The dump_callback function in SQLite 3.20.0 allows remote attackers to cause a denial of service (EXC_BAD_ACCESS and application crash) via a crafted file.

Remediation

Upgrade Debian:unstable sqlite3 to version 3.20.1-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: tar
Introduced through: tar@1.29b-1.1
Fixed in: 1.34+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: tar
Introduced through: tar@1.29b-1.1
Fixed in: 1.34+dfsg-1.4

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1.4 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Information Exposure

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/bsdutils@1:2.29-1

NVD Description

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

Remediation

There is no fixed version for Debian:unstable util-linux.

References

Information Exposure vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.36.1-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

An integer overflow in util-linux through 2.37.1 can potentially cause a buffer overflow if an attacker were able to use system resources in a way that leads to a large number in the /proc/sysvipc/sem file. NOTE: this is unexploitable in GNU C Library environments, and possibly in all realistic environments.

Remediation

Upgrade Debian:unstable util-linux to version 2.36.1-8 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Cryptographic Issues

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE.

Remediation

There is no fixed version for Debian:unstable openssl.

References

Cryptographic Issues vulnerability report

low severity

Insufficiently Protected Credentials

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Insufficiently Protected Credentials vulnerability report

low severity

Cryptographic Issues

Vulnerable module: glib2.0/libglib2.0-0
Introduced through: glib2.0/libglib2.0-0@2.50.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › glib2.0/libglib2.0-0@2.50.2-2

NVD Description

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

Remediation

There is no fixed version for Debian:unstable glib2.0.

References

Cryptographic Issues vulnerability report

low severity

Information Exposure

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Information Exposure vulnerability report

low severity

Use of Insufficiently Random Values

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Use of Insufficiently Random Values vulnerability report

low severity

Reachable Assertion

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.16.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.2-1 or higher.

References

Reachable Assertion vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.1+20191019-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

Remediation

Upgrade Debian:unstable ncurses to version 6.1+20191019-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

CVE-2016-20012

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product

Remediation

There is no fixed version for Debian:unstable openssh.

References

CVE-2016-20012 vulnerability report

low severity

Improper Authentication

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH 4.6 and earlier, when ChallengeResponseAuthentication is enabled, allows remote attackers to determine the existence of user accounts by attempting to authenticate via S/KEY, which displays a different response if the user account exists, a similar issue to CVE-2001-1483.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Improper Authentication vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:7.6p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly prevent write operations in readonly mode, which allows attackers to create zero-length files.

Remediation

Upgrade Debian:unstable openssh to version 1:7.6p1-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

Information Exposure

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

Information Exposure

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1e-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

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

Remediation

Upgrade Debian:unstable openssl to version 1.1.1e-1 or higher.

References

Information Exposure vulnerability report

low severity

Incorrect Permission Assignment for Critical Resource

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.7-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

An issue was discovered in shadow 4.5. newgidmap (in shadow-utils) is setuid and allows an unprivileged user to be placed in a user namespace where setgroups(2) is permitted. This allows an attacker to remove themselves from a supplementary group, which may allow access to certain filesystem paths if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. This flaw effectively reverts a security feature in the kernel (in particular, the /proc/self/setgroups knob) to prevent this sort of privilege escalation.

Remediation

Upgrade Debian:unstable shadow to version 1:4.7-1 or higher.

References

Incorrect Permission Assignment for Critical Resource vulnerability report

low severity

Improper Validation of Integrity Check Value

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Improper Validation of Integrity Check Value

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Improper Validation of Integrity Check Value

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:unstable systemd.

References

Improper Validation of Integrity Check Value vulnerability report

low severity

Cryptographic Issues

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

Remediation

There is no fixed version for Debian:unstable openssl.

References

Cryptographic Issues vulnerability report

low severity

CVE-2019-13057

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2
Fixed in: 2.4.48+dfsg-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

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

Remediation

Upgrade Debian:unstable openldap to version 2.4.48+dfsg-1 or higher.

References

CVE-2019-13057 vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: apr-util/libaprutil1
Introduced through: apr-util/libaprutil1@1.5.4-3
Fixed in: 1.6.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › apr-util/libaprutil1@1.5.4-3

NVD Description

Apache Portable Runtime Utility (APR-util) 1.6.0 and prior fail to validate the integrity of SDBM database files used by apr_sdbm*() functions, resulting in a possible out of bound read access. A local user with write access to the database can make a program or process using these functions crash, and cause a denial of service.

Remediation

Upgrade Debian:unstable apr-util to version 1.6.1-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Race Condition

Vulnerable module: coreutils
Introduced through: coreutils@8.26-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › coreutils@8.26-1

NVD Description

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

Remediation

There is no fixed version for Debian:unstable coreutils.

References

Race Condition vulnerability report

low severity

Improper Initialization

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

Remediation

There is no fixed version for Debian:unstable openldap.

References

Improper Initialization vulnerability report

low severity

Time-of-check Time-of-use (TOCTOU)

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.12.3+dfsg1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

Remediation

Upgrade Debian:unstable shadow to version 1:4.12.3+dfsg1-1 or higher.

References

Time-of-check Time-of-use (TOCTOU) vulnerability report

low severity

Improper Input Validation

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 237-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 237-1 or higher.

References

Improper Input Validation vulnerability report

low severity

Race Condition

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.29.2-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

Remediation

Upgrade Debian:unstable util-linux to version 2.29.2-1 or higher.

References

Race Condition vulnerability report

low severity

Link Following

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

Remediation

There is no fixed version for Debian:unstable systemd.

References

Link Following vulnerability report

low severity

Resource Management Errors

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

Remediation

There is no fixed version for Debian:unstable glibc.

References

Resource Management Errors vulnerability report

low severity

Improper Input Validation

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

Remediation

There is no fixed version for Debian:unstable gnutls28.

References

Improper Input Validation vulnerability report

low severity

Information Exposure

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.

Remediation

There is no fixed version for Debian:unstable openssh.

References

Information Exposure vulnerability report

low severity

Memory Leak

Vulnerable module: sqlite3/libsqlite3-0
Introduced through: sqlite3/libsqlite3-0@3.15.2-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › sqlite3/libsqlite3-0@3.15.2-2

NVD Description

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

Remediation

There is no fixed version for Debian:unstable sqlite3.

References

Memory Leak vulnerability report

low severity

Improper Certificate Validation

Vulnerable module: openldap/libldap-2.4-2
Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-2 and openldap/libldap-common@2.4.44+dfsg-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openldap/libldap-2.4-2@2.4.44+dfsg-2
Introduced through: golang@1.8-rc-stretch › openldap/libldap-common@2.4.44+dfsg-2

NVD Description

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

Remediation

There is no fixed version for Debian:unstable openldap.

References

Improper Certificate Validation vulnerability report

low severity

LDAP Injection

Vulnerable module: krb5/libgssapi-krb5-2
Introduced through: krb5/libgssapi-krb5-2@1.15-1, krb5/libk5crypto3@1.15-1 and others
Fixed in: 1.16.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

MIT krb5 1.6 or later allows an authenticated kadmin with permission to add principals to an LDAP Kerberos database to circumvent a DN containership check by supplying both a "linkdn" and "containerdn" database argument, or by supplying a DN string which is a left extension of a container DN string but is not hierarchically within the container DN.

Remediation

Upgrade Debian:unstable krb5 to version 1.16.1-1 or higher.

References

LDAP Injection vulnerability report

low severity

Improper Verification of Cryptographic Signature

Vulnerable module: apt
Introduced through: apt@1.4~beta3 and apt/libapt-pkg5.0@1.4~beta3

Detailed paths

Introduced through: golang@1.8-rc-stretch › apt@1.4~beta3
Introduced through: golang@1.8-rc-stretch › apt/libapt-pkg5.0@1.4~beta3

NVD Description

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

Remediation

There is no fixed version for Debian:unstable apt.

References

Improper Verification of Cryptographic Signature vulnerability report

low severity

Authentication Bypass

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.74.0-1.2

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1.2 or higher.

References

Authentication Bypass vulnerability report

low severity

CVE-2020-8284

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.74.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.

Remediation

Upgrade Debian:unstable curl to version 7.74.0-1 or higher.

References

CVE-2020-8284 vulnerability report

low severity

CVE-2022-35252

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.85.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Debian:unstable curl to version 7.85.0-1 or higher.

References

CVE-2022-35252 vulnerability report

low severity

CVE-2023-28322

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.88.1-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.

Remediation

Upgrade Debian:unstable curl to version 7.88.1-10 or higher.

References

CVE-2023-28322 vulnerability report

low severity

CVE-2023-38546

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.3.0-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

Remediation

Upgrade Debian:unstable curl to version 8.3.0-3 or higher.

References

CVE-2023-38546 vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.64.0-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

Remediation

Upgrade Debian:unstable curl to version 7.64.0-4 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

Use of Incorrectly-Resolved Name or Reference

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths case insensitively,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

low severity

Improper Authentication

Vulnerable module: openssh/openssh-client
Introduced through: openssh/openssh-client@1:7.4p1-5
Fixed in: 1:8.9p1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssh/openssh-client@1:7.4p1-5

NVD Description

An issue was discovered in OpenSSH before 8.9. If a client is using public-key authentication with agent forwarding but without -oLogLevel=verbose, and an attacker has silently modified the server to support the None authentication option, then the user cannot determine whether FIDO authentication is going to confirm that the user wishes to connect to that server, or that the user wishes to allow that server to connect to a different server on the user's behalf. NOTE: the vendor's position is "this is not an authentication bypass, since nothing is being bypassed.

Remediation

Upgrade Debian:unstable openssh to version 1:8.9p1-1 or higher.

References

Improper Authentication vulnerability report

low severity

Use of a Broken or Risky Cryptographic Algorithm

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 1.1.1d-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Remediation

Upgrade Debian:unstable openssl to version 1.1.1d-1 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: binutils
Introduced through: binutils@2.27.90.20170124-2
Fixed in: 2.37-3

Detailed paths

Introduced through: golang@1.8-rc-stretch › binutils@2.27.90.20170124-2

NVD Description

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.35.1. A heap-based buffer over-read can occur in bfd_getl_signed_32 in libbfd.c because sh_entsize is not validated in _bfd_elf_slurp_secondary_reloc_section in elf.c.

Remediation

Upgrade Debian:unstable binutils to version 2.37-3 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Integer Overflow or Wraparound

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.66.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

Integer overflow vulnerability in tool_operate.c in curl 7.65.2 via a large value as the retry delay. NOTE: many parties report that this has no direct security impact on the curl user; however, it may (in theory) cause a denial of service to associated systems or networks if, for example, --retry-delay is misinterpreted as a value much smaller than what was intended. This is not especially plausible because the overflow only happens if the user was trying to specify that curl should wait weeks (or longer) before trying to recover from a transient error.

Remediation

Upgrade Debian:unstable curl to version 7.66.0-1 or higher.

References

Integer Overflow or Wraparound vulnerability report

low severity

CVE-2019-1348

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.24.0-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

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. The --export-marks option of git fast-import is exposed also via the in-stream command feature export-marks=... and it allows overwriting arbitrary paths.

Remediation

Upgrade Debian:unstable git to version 1:2.24.0-2 or higher.

References

CVE-2019-1348 vulnerability report

low severity

Information Exposure

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.29-8

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.

Remediation

Upgrade Debian:unstable glibc to version 2.29-8 or higher.

References

Information Exposure vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: gnupg2/gpgv
Introduced through: gnupg2/gpgv@2.1.17-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnupg2/gpgv@2.1.17-2

NVD Description

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Debian:unstable gnupg2.

References

Out-of-bounds Write vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: libsepol/libsepol1
Introduced through: libsepol/libsepol1@2.6-2
Fixed in: 3.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libsepol/libsepol1@2.6-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libsepol package and not the libsepol package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

The CIL compiler in SELinux 3.2 has a heap-based buffer over-read in ebitmap_match_any (called indirectly from cil_check_neverallow). This occurs because there is sometimes a lack of checks for invalid statements in an optional block.

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Use After Free

Vulnerable module: libsepol/libsepol1
Introduced through: libsepol/libsepol1@2.6-2
Fixed in: 3.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libsepol/libsepol1@2.6-2

NVD Description

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __cil_verify_classpermission and __cil_pre_verify_helper).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Use After Free

Vulnerable module: libsepol/libsepol1
Introduced through: libsepol/libsepol1@2.6-2
Fixed in: 3.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libsepol/libsepol1@2.6-2

NVD Description

The CIL compiler in SELinux 3.2 has a use-after-free in __cil_verify_classperms (called from __verify_map_perm_classperms and hashtab_map).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Use After Free

Vulnerable module: libsepol/libsepol1
Introduced through: libsepol/libsepol1@2.6-2
Fixed in: 3.3-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › libsepol/libsepol1@2.6-2

NVD Description

The CIL compiler in SELinux 3.2 has a use-after-free in cil_reset_classpermission (called from cil_reset_classperms_set and cil_reset_classperms_list).

Remediation

Upgrade Debian:unstable libsepol to version 3.3-1 or higher.

References

Use After Free vulnerability report

low severity

Out-of-bounds Write

Vulnerable module: procps
Introduced through: procps@2:3.3.12-3 and procps/libprocps6@2:3.3.12-3
Fixed in: 2:4.0.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › procps@2:3.3.12-3
Introduced through: golang@1.8-rc-stretch › procps/libprocps6@2:3.3.12-3

NVD Description

Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.

Remediation

Upgrade Debian:unstable procps to version 2:4.0.4-1 or higher.

References

Out-of-bounds Write vulnerability report

low severity

Arbitrary Code Injection

Vulnerable module: shadow/login
Introduced through: shadow/login@1:4.2-3.3 and shadow/passwd@1:4.2-3.3
Fixed in: 1:4.13+dfsg1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › shadow/login@1:4.2-3.3
Introduced through: golang@1.8-rc-stretch › shadow/passwd@1:4.2-3.3

NVD Description

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

Remediation

Upgrade Debian:unstable shadow to version 1:4.13+dfsg1-2 or higher.

References

Arbitrary Code Injection vulnerability report

low severity

Out-of-bounds Read

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 240-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable.

Remediation

Upgrade Debian:unstable systemd to version 240-1 or higher.

References

Out-of-bounds Read vulnerability report

low severity

Missing Initialization of Resource

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.79.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

curl 7.7 through 7.76.1 suffers from an information disclosure when the -t command line option, known as CURLOPT_TELNETOPTIONS in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.

Remediation

Upgrade Debian:unstable curl to version 7.79.1-1 or higher.

References

Missing Initialization of Resource vulnerability report

low severity

Double Free

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others
Fixed in: 2.31-10

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The nameserver caching daemon (nscd) in the GNU C Library (aka glibc or libc6) 2.29 through 2.33, when processing a request for netgroup lookup, may crash due to a double-free, potentially resulting in degraded service or Denial of Service on the local system. This is related to netgroupcache.c.

Remediation

Upgrade Debian:unstable glibc to version 2.31-10 or higher.

References

Double Free vulnerability report

low severity

Out-of-Bounds

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 7.52.1-4

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

The ourWriteOut function in tool_writeout.c in curl 7.53.1 might allow physically proximate attackers to obtain sensitive information from process memory in opportunistic circumstances by reading a workstation screen during use of a --write-out argument ending in a '%' character, which leads to a heap-based buffer over-read.

Remediation

Upgrade Debian:unstable curl to version 7.52.1-4 or higher.

References

Out-of-Bounds vulnerability report

low severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 243-5

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.

Remediation

Upgrade Debian:unstable systemd to version 243-5 or higher.

References

Missing Release of Resource after Effective Lifetime vulnerability report

low severity

Use of Externally-Controlled Format String

Vulnerable module: git
Introduced through: git@1:2.11.0-2 and git/git-man@1:2.11.0-2
Fixed in: 1:2.40.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › git@1:2.11.0-2
Introduced through: golang@1.8-rc-stretch › git/git-man@1:2.11.0-2

NVD Description

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.

This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.

Remediation

Upgrade Debian:unstable git to version 1:2.40.1-1 or higher.

References

Use of Externally-Controlled Format String vulnerability report

low severity

new

CVE-2024-2004

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug.

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2004 vulnerability report

low severity

new

CVE-2024-2379

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2379 vulnerability report

low severity

new

CVE-2024-2398

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2398 vulnerability report

low severity

new

CVE-2024-2466

Vulnerable module: curl
Introduced through: curl@7.51.0-1 and curl/libcurl3-gnutls@7.51.0-1
Fixed in: 8.7.1-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › curl@7.51.0-1
Introduced through: golang@1.8-rc-stretch › curl/libcurl3-gnutls@7.51.0-1

NVD Description

libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc).

Remediation

Upgrade Debian:unstable curl to version 8.7.1-1 or higher.

References

CVE-2024-2466 vulnerability report

low severity

CVE-2024-25260

Vulnerable module: elfutils/libelf1
Introduced through: elfutils/libelf1@0.168-0.2

Detailed paths

Introduced through: golang@1.8-rc-stretch › elfutils/libelf1@0.168-0.2

NVD Description

elfutils v0.189 was discovered to contain a NULL pointer dereference via the handle_verdef() function at readelf.c.

Remediation

There is no fixed version for Debian:unstable elfutils.

References

CVE-2024-25260 vulnerability report

low severity

CVE-2024-28757

Vulnerable module: expat/libexpat1
Introduced through: expat/libexpat1@2.2.0-2
Fixed in: 2.6.1-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › expat/libexpat1@2.2.0-2

NVD Description

libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).

Remediation

Upgrade Debian:unstable expat to version 2.6.1-2 or higher.

References

CVE-2024-28757 vulnerability report

low severity

new

CVE-2024-2961

Vulnerable module: glibc/libc-bin
Introduced through: glibc/libc-bin@2.24-8, glibc/libc-dev-bin@2.24-9 and others

Detailed paths

Introduced through: golang@1.8-rc-stretch › glibc/libc-bin@2.24-8
Introduced through: golang@1.8-rc-stretch › glibc/libc-dev-bin@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/libc6-dev@2.24-9
Introduced through: golang@1.8-rc-stretch › glibc/multiarch-support@2.24-8

NVD Description

The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

Remediation

There is no fixed version for Debian:unstable glibc.

References

CVE-2024-2961 vulnerability report

low severity

new

Information Exposure

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.8.4-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

Information Exposure vulnerability report

low severity

new

Uncaught Exception

Vulnerable module: gnutls28/libgnutls30
Introduced through: gnutls28/libgnutls30@3.5.7-3
Fixed in: 3.8.4-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › gnutls28/libgnutls30@3.5.7-3

NVD Description

A flaw has been discovered in GnuTLS where an application crash can be induced when attempting to verify a specially crafted .pem bundle using the "certtool --verify-chain" command.

Remediation

Upgrade Debian:unstable gnutls28 to version 3.8.4-2 or higher.

References

Uncaught Exception vulnerability report

low severity

CVE-2024-26458

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

Remediation

There is no fixed version for Debian:unstable krb5.

References

CVE-2024-26458 vulnerability report

low severity

CVE-2024-26461

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Remediation

There is no fixed version for Debian:unstable krb5.

References

CVE-2024-26461 vulnerability report

low severity

CVE-2024-26462

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

Detailed paths

Introduced through: golang@1.8-rc-stretch › krb5/libgssapi-krb5-2@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libk5crypto3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5-3@1.15-1
Introduced through: golang@1.8-rc-stretch › krb5/libkrb5support0@1.15-1

NVD Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.

Remediation

There is no fixed version for Debian:unstable krb5.

References

CVE-2024-26462 vulnerability report

low severity

Information Exposure

Vulnerable module: libgcrypt20
Introduced through: libgcrypt20@1.7.5-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › libgcrypt20@1.7.5-2

NVD Description

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Debian:unstable libgcrypt20.

References

Information Exposure vulnerability report

low severity

CVE-2023-45918

Vulnerable module: ncurses/libncurses5
Introduced through: ncurses/libncurses5@6.0+20161126-1, ncurses/libncursesw5@6.0+20161126-1 and others
Fixed in: 6.4+20230625-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › ncurses/libncurses5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libncursesw5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/libtinfo5@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-base@6.0+20161126-1
Introduced through: golang@1.8-rc-stretch › ncurses/ncurses-bin@6.0+20161126-1

NVD Description

ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.

Remediation

Upgrade Debian:unstable ncurses to version 6.4+20230625-1 or higher.

References

CVE-2023-45918 vulnerability report

low severity

new

CVE-2024-28182

Vulnerable module: nghttp2/libnghttp2-14
Introduced through: nghttp2/libnghttp2-14@1.17.0-1
Fixed in: 1.61.0-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › nghttp2/libnghttp2-14@1.17.0-1

NVD Description

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.

Remediation

Upgrade Debian:unstable nghttp2 to version 1.61.0-1 or higher.

References

CVE-2024-28182 vulnerability report

low severity

CVE-2023-6237

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2
Fixed in: 3.1.5-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Debian:unstable openssl to version 3.1.5-1 or higher.

References

ADVISORY

CVE-2023-6237 vulnerability report

low severity

new

CVE-2024-2511

Vulnerable module: openssl
Introduced through: openssl@1.1.0c-2 and openssl/libssl1.1@1.1.0c-2

Detailed paths

Introduced through: golang@1.8-rc-stretch › openssl@1.1.0c-2
Introduced through: golang@1.8-rc-stretch › openssl/libssl1.1@1.1.0c-2

NVD Description

Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions

Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service

This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.

This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.

Remediation

There is no fixed version for Debian:unstable openssl.

References

CVE-2024-2511 vulnerability report

low severity

CVE-2023-50868

Vulnerable module: systemd/libsystemd0
Introduced through: systemd/libsystemd0@232-8 and systemd/libudev1@232-8
Fixed in: 255.4-1

Detailed paths

Introduced through: golang@1.8-rc-stretch › systemd/libsystemd0@232-8
Introduced through: golang@1.8-rc-stretch › systemd/libudev1@232-8

NVD Description

The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows remote attackers to cause a denial of service (CPU consumption for SHA-1 computations) via DNSSEC responses in a random subdomain attack, aka the "NSEC3" issue. The RFC 5155 specification implies that an algorithm must perform thousands of iterations of a hash function in certain situations.

Remediation

Upgrade Debian:unstable systemd to version 255.4-1 or higher.

References

CVE-2023-50868 vulnerability report

low severity

CVE-2023-39804

Vulnerable module: tar
Introduced through: tar@1.29b-1.1
Fixed in: 1.34+dfsg-1.3

Detailed paths

Introduced through: golang@1.8-rc-stretch › tar@1.29b-1.1

NVD Description

In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.

Remediation

Upgrade Debian:unstable tar to version 1.34+dfsg-1.3 or higher.

References

CVE-2023-39804 vulnerability report

low severity

new

CVE-2024-28085

Vulnerable module: util-linux
Introduced through: util-linux@2.29-1, util-linux/libblkid1@2.29-1 and others
Fixed in: 2.39.3-11

Detailed paths

Introduced through: golang@1.8-rc-stretch › util-linux@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libblkid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libfdisk1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libmount1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libsmartcols1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/libuuid1@2.29-1
Introduced through: golang@1.8-rc-stretch › util-linux/mount@2.29-1

NVD Description

wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.

Remediation

Upgrade Debian:unstable util-linux to version 2.39.3-11 or higher.

References

CVE-2024-28085 vulnerability report

Vulnerabilities

Dependencies

Source

Target OS

critical severity new

Embedded Malicious Code

Detailed paths

NVD Description

Remediation

References

critical severity

Integer Overflow or Wraparound

Detailed paths

NVD Description

Remediation

References

critical severity

Out-of-bounds Write

Detailed paths

NVD Description

Remediation

References

critical severity

Buffer Overflow

Detailed paths

NVD Description

Remediation

References

critical severity

CVE-2018-1000007

Detailed paths

NVD Description

Remediation

References

critical severity

Double Free

Detailed paths

NVD Description

Remediation

References

critical severity

Exposure of Resource to Wrong Sphere

Detailed paths

NVD Description

Remediation

References

critical severity

Incorrect Default Permissions

Detailed paths

NVD Description

Remediation

References

critical severity

Integer Overflow or Wraparound

Detailed paths

NVD Description

Remediation

References

critical severity

Integer Overflow or Wraparound

Detailed paths

NVD Description

Remediation

References

critical severity

Out-of-Bounds

Detailed paths

NVD Description

Remediation

References

critical severity

Out-of-Bounds

Detailed paths

NVD Description

Remediation

References

critical severity

Out-of-bounds Read

Detailed paths

NVD Description

critical severity

new