Vulnerabilities

621 via 1272 paths

Dependencies

213

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:9
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 41
  • 136
  • 106
  • 338
Status
  • 621
  • 0
  • 0
OS binaries
  • 575
  • 46

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 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:9 curl to version 7.52.1-5+deb9u10 or higher.

References

critical severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 curl to version 7.52.1-5+deb9u10 or higher.

References

critical severity

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.18.25
  • Fixed in: 1.18.26

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z dpkg@1.18.25

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:9 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:9 dpkg to version 1.18.26 or higher.

References

critical severity

Exposure of Resource to Wrong Sphere

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 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:9 expat to version 2.2.0-2+deb9u5 or higher.

References

critical severity

Improper Encoding or Escaping of Output

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u5 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u5 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u5 or higher.

References

critical severity

CVE-2019-1353

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u5 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 libidn to version 1.33-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. A heap-based buffer overflow in function WebPDecodeRGBInto is possible due to an invalid check for buffer size. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in PutLE16().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Use After Free

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. A use-after-free was found due to a thread being killed too early. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Use of Uninitialized Resource

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A use of uninitialized value was found in libwebp in versions before 1.0.1 in ReadSymbol().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-6@2:1.6.4-3+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-data@2:1.6.4-3+deb9u1

NVD Description

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

LookupCol.c in X.Org X through X11R7.7 and libX11 before 1.7.1 might allow remote attackers to execute arbitrary code. The libX11 XLookupColor request (intended for server-side color lookup) contains a flaw allowing a client to send color-name requests with a name longer than the maximum size allowed by the protocol (and also longer than the maximum packet size for normal-sized packets). The user-controlled data exceeding the maximum size is then interpreted by the server as additional X protocol requests and executed, e.g., to disable X server authorization completely. For example, if the victim encounters malicious terminal control sequences for color codes, then the attacker may be able to take full control of the running graphical session.

Remediation

Upgrade Debian:9 libx11 to version 2:1.6.4-3+deb9u4 or higher.

References

critical severity

CVE-2019-11068

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1.1@1.1.29-2.1

NVD Description

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

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

Remediation

Upgrade Debian:9 libxslt to version 1.1.29-2.1+deb9u1 or higher.

References

critical severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@0.0~r131-2+b1
  • Fixed in: 0.0~r131-2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z lz4/liblz4-1@0.0~r131-2+b1

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:9 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:9 lz4 to version 0.0~r131-2+deb9u1 or higher.

References

critical severity

Integer Overflow or Wraparound

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

Detailed paths

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

NVD Description

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

NGINX before 1.13.6 has a buffer overflow for years that exceed four digits, as demonstrated by a file with a modification date in 1969 that causes an integer overflow (or a false modification date far in the future), when encountered by the autoindex module.

Remediation

Upgrade Debian:9 nginx to version 1.10.3-1+deb9u7 or higher.

References

critical severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 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:9 openldap to version 2.4.44+dfsg-5+deb9u9 or higher.

References

critical severity

OS Command Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u6 or higher.

References

critical severity

OS Command Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 openssl.

References

critical severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 openssl.

References

critical severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u6 or higher.

References

critical severity

CVE-2019-9636

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

critical severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 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:9 shadow to version 1:4.4-4.1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libbsd/libbsd0
  • Introduced through: libbsd/libbsd0@0.8.3-1
  • Fixed in: 0.8.3-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 libbsd to version 0.8.3-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ShiftBytes().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE16().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkVerifyAndAssign. The highest threat from this vulnerability is to data confidentiality and to the service availability.

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in ApplyFilter().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. An out-of-bounds read was found in function ChunkAssignData. The highest threat from this vulnerability is to data confidentiality and to the service availability.

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1
  • Fixed in: 0.5.2-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().

Remediation

Upgrade Debian:9 libwebp to version 0.5.2-1+deb9u1 or higher.

References

critical severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

critical severity

Directory Traversal

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

high severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3

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:9 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:9 cyrus-sasl2 to version 2.1.27~101-g0780600+dfsg-3+deb9u2 or higher.

References

high severity

Incorrect Calculation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

CVE-2019-1387

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u5 or higher.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u5 or higher.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 git to version 1:2.11.0-3+deb9u5 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: gzip/gzip
  • Introduced through: gzip/gzip@1.6-5+b1
  • Fixed in: 1.6-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gzip/gzip@1.6-5+b1

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:9 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:9 gzip to version 1.6-5+deb9u1 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/icu-devtools@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/libicu-dev@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/libicu57@57.1-6+deb9u2

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:9 relevant fixed versions and status.

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:9 icu to version 57.1-6+deb9u4 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u6 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u4 or higher.

References

high severity

Incomplete Cleanup

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

A flaw was found in PostgreSQL. There is an issue with incomplete efforts to operate safely when a privileged user is maintaining another user's objects. The Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck commands activated relevant protections too late or not at all during the process. This flaw allows an attacker with permission to create non-temporary objects in at least one schema to execute arbitrary SQL functions under a superuser identity.

Remediation

There is no fixed version for Debian:9 postgresql-9.6.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.22-0+deb9u1 or higher.

References

high severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.20-0+deb9u1 or higher.

References

high severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.15-0+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7, 4.0.8 and 4.0.9 allows remote attackers to cause a denial of service (crash) or possibly have unspecified other impact via a crafted TIFF file.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

high severity

Improper Input Validation

  • Vulnerable module: xz-utils/liblzma5
  • Introduced through: xz-utils/liblzma5@5.2.2-1.2+b1 and xz-utils/xz-utils@5.2.2-1.2+b1
  • Fixed in: 5.2.2-1.2+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z xz-utils/liblzma5@5.2.2-1.2+b1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z xz-utils/xz-utils@5.2.2-1.2+b1

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:9 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:9 xz-utils to version 5.2.2-1.2+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u4 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-modules-5.24@5.24.1-3+deb9u5

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:9 relevant fixed versions and status.

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:9 perl to version 5.24.1-3+deb9u7 or higher.

References

high severity

Privilege Escalation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Privilege Escalation under certain conditions on Windows platforms. More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different escalation attacks: PATH variable hijacking and DLL hijacking.

Remediation

Upgrade node to version 16.4.1, 14.17.2, 12.22.2 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Out-of-bounds Read in libuv's uv__idna_toascii() function which is used to convert strings to ASCII. This is called by Node's dns module's lookup() function and can lead to information disclosures or crashes.

Remediation

Upgrade node to version 16.4.1, 14.17.2, 12.22.2 or higher.

References

high severity

Prototype Pollution

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution via console.table properties. Due to the formatting logic of the console.table() function it was not safe to allow user controlled input to be passed to the properties parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be __proto__. Note: This vulnerability only allows an empty string to be assigned numerical keys of the object prototype.

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade node to version 12.22.9, 14.18.3, 16.13.2, 17.3.1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-modules-5.24@5.24.1-3+deb9u5

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:9 relevant fixed versions and status.

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:9 perl to version 5.24.1-3+deb9u7 or higher.

References

high severity

Missing Authentication for Critical Function

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

high severity

Information Exposure

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

Detailed paths

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

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 gcc-6.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

libjpeg-turbo 2.0.4, and mozjpeg 4.0.0, has a heap-based buffer over-read in get_rgb_row() in rdppm.c via a malformed PPM input file.

Remediation

Upgrade Debian:9 libjpeg-turbo to version 1:1.5.1-2+deb9u1 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u2 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 libssh2 to version 1.7.0-1+deb9u2 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libhogweed4@3.3-1+b2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libnettle6@3.3-1+b2

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:9 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:9 nettle to version 3.3-1+deb9u1 or higher.

References

high severity

Arbitrary File Overwrite

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

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

Details

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

Directory Traversal vulnerabilities can be generally divided into two types:

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

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

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

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

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

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

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

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

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

Remediation

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

References

high severity

Arbitrary File Write

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

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

Details

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

Directory Traversal vulnerabilities can be generally divided into two types:

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

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

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

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

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

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

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

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

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

Remediation

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

References

high severity

Code Injection

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Code Injection due to the incorrect handling of environment variables on Linux when the process is running with elevated privileges that the current user lacks (does not apply to CAP_NET_BIND_SERVICE).

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

high severity

SQL Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

When the server is configured to use trust authentication with a clientcert requirement or to use cert authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of SSL certificate verification and encryption.

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.24-0+deb9u1 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.20-0+deb9u1 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u11 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u10 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

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

Remediation

Upgrade Debian:9 libjpeg-turbo to version 1:1.5.1-2+deb9u2 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-6@2:1.6.4-3+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-data@2:1.6.4-3+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 libx11 to version 2:1.6.4-3+deb9u3 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u4 or higher.

References

high severity

Improper Privilege Management

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 relevant fixed versions and status.

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:9 shadow to version 1:4.4-4.1+deb9u1 or higher.

References

high severity

Deserialization of Untrusted Data

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd to version 232-25+deb9u10 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd to version 232-25+deb9u14 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

An integer overflow flaw was found in libtiff that exists in the tif_getimage.c file. This flaw allows an attacker to inject and execute arbitrary code when a user opens a crafted TIFF file. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u6 or higher.

References

high severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

A heap-based buffer overflow flaw was found in libtiff in the handling of TIFF images in libtiff's TIFF2PDF tool. A specially crafted TIFF file can lead to arbitrary code execution. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u6 or higher.

References

high severity

Off-by-one Error

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

Detailed paths

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

NVD Description

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

A security issue in nginx resolver was identified, which might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or potential other impact.

Remediation

Upgrade Debian:9 nginx to version 1.10.3-1+deb9u6 or higher.

References

high severity

Arbitrary Command Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9

Remediation

There is no fixed version for Debian:9 python2.7.

References

high severity

Cleartext Transmission of Sensitive Information

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u16 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u13 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u13 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u12 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z cyrus-sasl2/libsasl2-2@2.1.27~101-g0780600+dfsg-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z cyrus-sasl2/libsasl2-modules-db@2.1.27~101-g0780600+dfsg-3

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:9 relevant fixed versions and status.

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:9 cyrus-sasl2 to version 2.1.27~101-g0780600+dfsg-3+deb9u1 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function.

Remediation

Upgrade Debian:9 expat to version 2.2.0-2+deb9u4 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u3 or higher.

References

high severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u2 or higher.

References

high severity

Insufficiently Protected Credentials

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u6 or higher.

References

high severity

Insufficiently Protected Credentials

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u7 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: gmp/libgmp10
  • Introduced through: gmp/libgmp10@2:6.1.2+dfsg-1
  • Fixed in: 2:6.1.2+dfsg-1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 gmp to version 2:6.1.2+dfsg-1+deb9u1 or higher.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnutls28/libgnutls30@3.5.8-5+deb9u4

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:9 relevant fixed versions and status.

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:9 gnutls28 to version 3.5.8-5+deb9u5 or higher.

References

high severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5 to version 1.15-1+deb9u2 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u6 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

high severity

Memory Leak

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

high severity

Missing Release of Resource after Effective Lifetime

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u6 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1.1@1.1.29-2.1

NVD Description

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

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

Remediation

Upgrade Debian:9 libxslt to version 1.1.29-2.1+deb9u2 or higher.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libhogweed4@3.3-1+b2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libnettle6@3.3-1+b2

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:9 relevant fixed versions and status.

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:9 nettle to version 3.3-1+deb9u1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nghttp2/libnghttp2-14@1.18.1-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:9 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:9 nghttp2 to version 1.18.1-1+deb9u1 or higher.

References

high severity

CVE-2019-9513

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nghttp2/libnghttp2-14@1.18.1-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:9 relevant fixed versions and status.

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:9 nghttp2 to version 1.18.1-1+deb9u1 or higher.

References

high severity

Improper Enforcement of Message or Data Structure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nghttp2/libnghttp2-14@1.18.1-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:9 relevant fixed versions and status.

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:9 nghttp2 to version 1.18.1-1+deb9u2 or higher.

References

high severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nghttp2/libnghttp2-14@1.18.1-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:9 relevant fixed versions and status.

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:9 nghttp2 to version 1.18.1-1+deb9u2 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian. See How to fix? for Debian:9 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:9 nginx to version 1.10.3-1+deb9u3 or higher.

References

high severity

CVE-2019-9513

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

Detailed paths

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

NVD Description

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

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:9 nginx to version 1.10.3-1+deb9u3 or higher.

References

high severity

HTTP Request Smuggling

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

Detailed paths

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

NVD Description

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

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

Remediation

Upgrade Debian:9 nginx to version 1.10.3-1+deb9u5 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to a lack of safeguards on chunk extension bytes. The server may read an unbounded number of bytes from a single connection, which allows an attacker to cause denial of service via CPU and network bandwidth exhaustion.

Details

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

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

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

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

Two common types of DoS vulnerabilities:

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

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

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

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

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

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

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

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

Remediation

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

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

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

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

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

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

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

Remediation

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

References

high severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Remediation

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

References

high severity

Key Management Errors

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Key Management Errors. 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.

Remediation

Upgrade node to version 10.9.0 or higher.

References

high severity

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

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

CVE-2019-13565

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u3 or higher.

References

high severity

CVE-2020-36226

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Integer Underflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Integer Underflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u5 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u6 or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u6 or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u8 or higher.

References

high severity

Release of Invalid Pointer or Reference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u7 or higher.

References

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u4 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u3 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u5 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u4 or higher.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u7 or higher.

References

high severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 p11-kit to version 0.23.3-2+deb9u1 or higher.

References

high severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-modules-5.24@5.24.1-3+deb9u5

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:9 relevant fixed versions and status.

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:9 perl to version 5.24.1-3+deb9u7 or higher.

References

high severity

Permissive Whitelist

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.20-0+deb9u1 or higher.

References

high severity

Directory Traversal

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip@9.0.1-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip/python-pip-whl@9.0.1-2

NVD Description

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

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

Remediation

Upgrade Debian:9 python-pip to version 9.0.1-2+deb9u2 or higher.

References

high severity

CVE-2019-16056

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

high severity

Improper Handling of Exceptional Conditions

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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

Remediation

Upgrade Debian:9 sqlite3 to version 3.16.2-5+deb9u3 or higher.

References

high severity

Improper Initialization

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the "invertImage()" function in the component "tiffcrop".

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u7 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.8.dfsg-5
  • Fixed in: 1:1.2.8.dfsg-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z zlib/zlib1g@1:1.2.8.dfsg-5

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:9 relevant fixed versions and status.

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Debian:9 zlib to version 1:1.2.8.dfsg-5+deb9u1 or higher.

References

high severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Certificate Validation. There is insufficient verification of a certificate chain when using the X509_V_FLAG_X509_STRICT flag.

Remediation

Upgrade node to version 15.14.0, 14.16.1, 12.22.1, 10.24.1 or higher.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Use After Free on close http2 on stream canceling. An attacker might be able to exploit the memory corruption to change process behaviour.

The issue follows on from CVE-2021-22930 as the fix for it did not completely resolve the vulnerability.

Remediation

Upgrade node to version 16.6.2, 14.17.5, 12.22.5 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u4 or higher.

References

high severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0k-1~deb9u1 or higher.

References

high severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u6 or higher.

References

high severity

Untrusted Search Path

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.19-0+deb9u1 or higher.

References

high severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption.

Remediation

Upgrade Debian:9 libjpeg-turbo to version 1:1.5.1-2+deb9u1 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

A heap buffer overflow in ExtractImageSection function in tiffcrop.c in libtiff library Version 4.3.0 allows attacker to trigger unsafe or out of bounds memory access via crafted TIFF image file which could result into application crash, potential information disclosure or any other context-dependent impact

Remediation

There is no fixed version for Debian:9 tiff.

References

high severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

high severity

Improper Authorization

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd to version 232-25+deb9u11 or higher.

References

medium severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/e2fslibs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libcomerr2@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libss2@1.43.4-2

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:9 relevant fixed versions and status.

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:9 e2fsprogs to version 1.43.4-2+deb9u1 or higher.

References

medium severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/e2fslibs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libcomerr2@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libss2@1.43.4-2

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:9 relevant fixed versions and status.

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:9 e2fsprogs to version 1.43.4-2+deb9u2 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-6@2:1.6.4-3+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libx11/libx11-data@2:1.6.4-3+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 libx11 to version 2:1.6.4-3+deb9u2 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

medium severity

Insufficiently Protected Credentials

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

medium severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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:9 expat to version 2.2.0-2+deb9u5 or higher.

References

medium severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z freetype/libfreetype6@2.6.3-3.2

NVD Description

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

Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Remediation

Upgrade Debian:9 freetype to version 2.6.3-3.2+deb9u2 or higher.

References

medium severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg-agent@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gpgv@2.1.18-8~deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 gnupg2.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5 to version 1.15-1+deb9u3 or higher.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

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

Remediation

Upgrade Debian:9 libjpeg-turbo to version 1:1.5.1-2+deb9u1 or higher.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

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

Remediation

Upgrade Debian:9 libjpeg-turbo to version 1:1.5.1-2+deb9u1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

medium severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u5 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u7 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u3 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

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

NVD Description

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

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

Remediation

Upgrade Debian:9 nginx to version 1.10.3-1+deb9u3 or higher.

References

medium severity

Buffer Overflow

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Remediation

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

References

medium severity

Hostname Spoofing

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Remediation

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

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to HTTP Request Smuggling via llhttp. The HTTP parser accepts requests with a space (SP) right after the header name before the colon.

Remediation

Upgrade node to version 12.22.7, 14.18.1, 16.11.1 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to HTTP Request Smuggling via llhttp. The parse ignores chunk extensions when parsing the body of chunked requests.

Remediation

Upgrade node to version 12.22.7, 14.18.1, 16.11.1 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to HTTP Request Smuggling when the llhttp parser in the http module does not correctly parse and validate Transfer-Encoding headers.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to HTTP Request Smuggling. The llhttp parser in the http module does not correctly handle multi-line Transfer-Encoding headers.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to HTTP Request Smuggling. when the llhttp parser in the http module does not adequately delimit HTTP requests with CRLF sequences.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

HTTP request splitting

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Remediation

Upgrade node to version 6.15.0, 8.14.0 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

A flaw was found in postgresql. Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an authenticated database user could read arbitrary bytes of server memory. The highest threat from this vulnerability is to data confidentiality.

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.22-0+deb9u1 or higher.

References

medium severity

Missing Authorization

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.17-0+deb9u1 or higher.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

medium severity

CVE-2019-7663

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.4.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f3a5e010.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Improper Resource Shutdown or Release

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

A vulnerability classified as problematic was found in LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u5 or higher.

References

medium severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the 'in _TIFFmemcpy' funtion in the component 'tif_unix.c'.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u7 or higher.

References

medium severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Reachable Assertion in tiffcp in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 5e180045.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

CRLF Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

medium severity

CRLF Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

medium severity

Cross-site Scripting (XSS)

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u5 or higher.

References

medium severity

Stack-based Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

A stack buffer overflow flaw was found in Libtiffs' tiffcp.c in main() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffcp tool, triggering a stack buffer overflow issue, possibly corrupting the memory, and causing a crash that leads to a denial of service.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Insufficient Verification of Data Authenticity

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u16 or higher.

References

medium severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgcrypt20@1.7.6-2+deb9u3

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:9 relevant fixed versions and status.

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:9 libgcrypt20 to version 1.7.6-2+deb9u4 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u4 or higher.

References

medium severity

DLL Hijacking

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to DLL Hijacking. on Windows based systems running OpenSSL that use a C:\Program Files\Common Files\SSL\openssl.cnf file. Attackers could place a malicious providers.dll file at one of the locations checked according to DLL Search Order and it would be used by the application.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

DNS Rebinding

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to DNS Rebinding by bypassing IsAllowedHost because IsIPAddress does not properly check if an IP address is invalid or not. This vulnerability is a bypass of CVE-2021-22884.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to NULL Pointer Dereference. If sent a maliciously crafted renegotiation ClientHello message from a client, an OpenSSL TLS server may crash. 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.

Remediation

Upgrade node to version 15.14.0, 14.16.1, 12.22.1, 10.24.1 or higher.

References

medium severity

Observable Timing Discrepancy

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Observable Timing Discrepancy due to the implementation of PKCS#1 v1.5 padding. An attacker can infer the private key used in the cryptographic operation by observing the time taken to execute cryptographic operations (Marvin).

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

medium severity

Use After Free

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

Remediation

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

References

medium severity

CVE-2021-4160

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 openssl.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u3 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u2 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u4 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u3 or higher.

References

medium severity

Insufficiently Protected Credentials

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

A man-in-the-middle attacker can inject false responses to the client's first few queries, despite the use of SSL certificate verification and encryption.

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.24-0+deb9u1 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u5 or higher.

References

medium severity

Race Condition

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd to version 232-25+deb9u10 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/libapt-pkg5.0@1.4.9

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:9 relevant fixed versions and status.

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:9 apt to version 1.4.11 or higher.

References

medium severity

Insufficiently Protected Credentials

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

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

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

Remediation

Upgrade node to version 6.17.0, 8.15.1 or higher.

References

medium severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/libapt-pkg5.0@1.4.9

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:9 relevant fixed versions and status.

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:9 apt to version 1.4.10 or higher.

References

medium severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/icu-devtools@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/libicu-dev@57.1-6+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z icu/libicu57@57.1-6+deb9u2

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:9 relevant fixed versions and status.

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:9 icu to version 57.1-6+deb9u5 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

The PPM reader in libjpeg-turbo through 2.0.90 mishandles use of tjLoadImage for loading a 16-bit binary PPM file into a grayscale buffer and loading a 16-bit binary PGM file into an RGB buffer. This is related to a heap-based buffer overflow in the get_word_rgb_row function in rdppm.c.

Remediation

There is no fixed version for Debian:9 libjpeg-turbo.

References

medium severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u6 or higher.

References

medium severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.

Remediation

Upgrade Debian:9 sqlite3 to version 3.16.2-5+deb9u2 or higher.

References

medium severity

NULL Pointer Dereference

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

medium severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd to version 232-25+deb9u13 or higher.

References

medium severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Divide By Zero error in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f8d0f9aa.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFReadDirectory() in tif_dirread.c in libtiff versions from 4.0 to 4.3.0 could lead to Denial of Service via crafted TIFF file. For users that compile libtiff from sources, a fix is available with commit 561599c.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u8 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFFetchStripThing() in tif_dirread.c in libtiff versions from 3.9.0 to 4.3.0 could lead to Denial of Service via crafted TIFF file. For users that compile libtiff from sources, the fix is available with commit eecb0712.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u8 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Null source pointer passed as an argument to memcpy() function within TIFFFetchNormalTag () in tif_dirread.c in libtiff versions up to 4.3.0 could lead to Denial of Service via crafted TIFF file.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF 4.3.0 has an out-of-bounds read in _TIFFmemcpy in tif_unix.c in certain situations involving a custom tag and 0x0200 as the second word of the DE field.

Remediation

Upgrade Debian:9 tiff to version 4.0.8-2+deb9u8 or higher.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Out-of-bounds Read error in tiffcp in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 408976c4.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

A heap buffer overflow flaw was found in Libtiffs' tiffinfo.c in TIFFReadRawDataStriped() function. This flaw allows an attacker to pass a crafted TIFF file to the tiffinfo tool, triggering a heap buffer overflow issue and causing a crash that leads to a denial of service.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:619, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit b4e79bfa.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF master branch has an out-of-bounds read in LZWDecode in libtiff/tif_lzw.c:624, allowing attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit b4e79bfa.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Unchecked Return Value

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

Unchecked Return Value to NULL Pointer Dereference in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit f2b656e2.

Remediation

There is no fixed version for Debian:9 tiff.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u14 or higher.

References

medium severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5 to version 1.15-1+deb9u3 or higher.

References

medium severity

Use of Uninitialized Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

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

Remediation

Upgrade Debian:9 libgd2 to version 2.2.4-2+deb9u5 or higher.

References

medium severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

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

png_image_free in png.c in libpng 1.6.x before 1.6.37 has a use-after-free because png_image_free_function is called under png_safe_execute.

Remediation

Upgrade Debian:9 libpng1.6 to version 1.6.28-1+deb9u1 or higher.

References

medium severity

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

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1.1@1.1.29-2.1

NVD Description

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

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

Remediation

Upgrade Debian:9 libxslt to version 1.1.29-2.1+deb9u1 or higher.

References

medium severity

Use of Uninitialized Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1.1@1.1.29-2.1

NVD Description

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

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

Remediation

Upgrade Debian:9 libxslt to version 1.1.29-2.1+deb9u1 or higher.

References

medium severity

HTTP Request Smuggling

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

Detailed paths

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

NVD Description

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

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

Remediation

Upgrade Debian:9 nginx to version 1.10.3-1+deb9u4 or higher.

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Certificate Validation which is not handling multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects in order to inject a Common Name that would allow bypassing the certificate subject verification.

Remediation

Upgrade node to version 12.22.9, 14.18.3, 16.13.2, 17.3.1 or higher.

References

medium severity

Improper Certificate Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Certificate Validation via string injection. Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.

Remediation

Upgrade node to version 12.22.9, 14.18.3, 16.13.2, 17.3.1 or higher.

References

medium severity

Improper Handling of URL Encoding

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Handling of URL Encoding via Subject Alternative Name (SAN) types, which PKIs are not defined to use. That, can result in bypassing name-constrained intermediates. Additionally, when a protocol allows URI SANs, node does not match the URI correctly.

Remediation

Upgrade node to version 12.22.9, 14.18.3, 16.13.2, 17.3.1 or higher.

References

medium severity

Improper Input Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Input Validation. If the Node.js https API was used incorrectly and undefined was in passed for the rejectUnauthorized parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

Remediation

Upgrade node to version 16.6.2, 14.17.5, 12.22.5 or higher.

References

medium severity

Inconsistency Between Implementation and Documented Design

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Inconsistency Between Implementation and Documented Design where the generateKeys() API function returned from crypto.createDiffieHellman() do not generate keys after setting a private key.

Remediation

Upgrade node to version 16.20.1, 18.16.1, 20.3.1 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Information Exposure in the aesni_ocb_encrypt and aesni_ocb_decrypt, which reveal 16 unencrypted bytes of memory.

NOTE: Implementations using TLS or DTLS are not affected by this vulnerability.

Remediation

Upgrade node to version 14.20.0, 16.16.0, 18.5.0 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u5 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2u-1~deb9u1 or higher.

References

medium severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 p11-kit to version 0.23.3-2+deb9u1 or higher.

References

medium severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

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

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

medium severity

Unchecked Return Value

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

A flaw was found in Python, specifically in the FTP (File Transfer Protocol) client library in PASV (passive) mode. The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u6 or higher.

References

medium severity

Improper Input Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Input Validation due to missing input validation of host names returned by Domain Name Servers in the Node.js DNS library. It could lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library.

NOTE: This vulnerability has also been identified as: CVE-2021-3672

Remediation

Upgrade node to version 16.6.2, 14.17.5, 12.22.5 or higher.

References

medium severity

Improper Input Validation

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

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

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

Affected versions of this package are vulnerable to Improper Input Validation due to missing input validation of host names returned by Domain Name Servers in the Node.js DNS library. It could lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library.

NOTE: This vulnerability has also been identified as: CVE-2021-22931

Remediation

Upgrade node to version 16.6.2, 14.17.5, 12.22.5 or higher.

References

medium severity

CVE-2019-13057

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap to version 2.4.44+dfsg-5+deb9u3 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5 to version 1.15-1+deb9u3 or higher.

References

medium severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2@2.9.4+dfsg1-2.2+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxml2/libxml2-dev@2.9.4+dfsg1-2.2+deb9u2

NVD Description

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

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

Remediation

Upgrade Debian:9 libxml2 to version 2.9.4+dfsg1-2.2+deb9u6 or higher.

References

medium severity

CVE-2019-1547

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u1 or higher.

References

medium severity

CVE-2019-1547

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

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

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:9 openssl1.0 to version 1.0.2t-1~deb9u1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-1.1
  • Fixed in: 1.29b-1.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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:9 tar to version 1.29b-1.1+deb9u1 or higher.

References

medium severity

Improper Access Control

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

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

Remediation

Upgrade Debian:9 postgresql-9.6 to version 9.6.13-0+deb9u1 or higher.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z bzip2/libbz2-1.0@1.0.6-8.1

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:9 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

There is no fixed version for Debian:9 bzip2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: db5.3/libdb5.3
  • Introduced through: db5.3/libdb5.3@5.3.28-12+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z db5.3/libdb5.3@5.3.28-12+deb9u1

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:9 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

There is no fixed version for Debian:9 db5.3.

References

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.6.3-3.2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z freetype/libfreetype6@2.6.3-3.2

NVD Description

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

FreeType commit 1e2eb65048f75c64b68708efed6ce904c31f3b2f was discovered to contain a heap buffer overflow via the function sfnt_init_face.

Remediation

There is no fixed version for Debian:9 freetype.

References

low severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 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

There is no fixed version for Debian:9 glibc.

References

low severity

Buffer Overflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 krb5.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 krb5.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 libpng1.6.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 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

There is no fixed version for Debian:9 sqlite3.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 sqlite3.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

CVE-2005-2541

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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:9 tar.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

In LibTIFF 4.0.7, the program processes BMP images without verifying that biWidth and biHeight in the bitmap-information header match the actual input, leading to a heap-based buffer over-read in bmp2tiff.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:9 git.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:9 git.

References

low severity

CVE-2019-1010023

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Cross-site Request Forgery (CSRF)

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg-agent@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gpgv@2.1.18-8~deb9u4

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:9 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

There is no fixed version for Debian:9 gnupg2.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

Libjpeg-turbo all version have a stack-based buffer overflow in the "transform" component. A remote attacker can send a malformed jpeg file to the service and cause arbitrary code execution or denial of service of the target service.

Remediation

There is no fixed version for Debian:9 libjpeg-turbo.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 libpng1.6.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-bin@6.0+20161126-1+deb9u2

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:9 relevant fixed versions and status.

An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.

Remediation

There is no fixed version for Debian:9 ncurses.

References

low severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

Lib/webbrowser.py in Python through 3.6.3 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL. NOTE: a software maintainer indicates that exploitation is impossible because the code relies on subprocess.Popen and the default shell=False setting

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

The TIFFFdOpen function in tif_unix.c in LibTIFF 4.0.10 has a memory leak, as demonstrated by pal2rgb.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF version 4.0.7 is vulnerable to a heap-based buffer over-read in tif_lzw.c resulting in DoS or code execution via a crafted bmp image to tools/bmp2tiff.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Link Following

  • Vulnerable module: python-defaults/libpython-stdlib
  • Introduced through: python-defaults/libpython-stdlib@2.7.13-2, python-defaults/python@2.7.13-2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-defaults/libpython-stdlib@2.7.13-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-defaults/python@2.7.13-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-defaults/python-minimal@2.7.13-2

NVD Description

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

Tools/faqwiz/move-faqwiz.sh (aka the generic FAQ wizard moving tool) in Python 2.4.5 might allow local users to overwrite arbitrary files via a symlink attack on a tmp$RANDOM.tmp temporary file. NOTE: there may not be common usage scenarios in which tmp$RANDOM.tmp is located in an untrusted directory.

Remediation

There is no fixed version for Debian:9 python-defaults.

References

low severity

Integer Underflow

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 libgd2.

References

low severity

Out-of-bounds Write

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@0.0~r131-2+b1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z lz4/liblz4-1@0.0~r131-2+b1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 lz4.

References

low severity

Improper Check for Dropped Privileges

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z bash@4.4-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 bash.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Incorrect Type Conversion or Cast

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/e2fslibs@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libcomerr2@1.43.4-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z e2fsprogs/libss2@1.43.4-2

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:9 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

There is no fixed version for Debian:9 e2fsprogs.

References

low severity

Out-of-bounds Write

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.6.3-3.2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z freetype/libfreetype6@2.6.3-3.2

NVD Description

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

ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.

Remediation

There is no fixed version for Debian:9 freetype.

References

low severity

Uncontrolled Search Path Element

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 git.

References

low severity

Improper Resource Shutdown or Release

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Off-by-one Error

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

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:9 pcre3.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

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:9 pcre3.

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-modules-5.24@5.24.1-3+deb9u5

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:9 relevant fixed versions and status.

CPAN 2.28 allows Signature Verification Bypass.

Remediation

There is no fixed version for Debian:9 perl.

References

low severity

Improper Input Validation

  • Vulnerable module: python-pip
  • Introduced through: python-pip@9.0.1-2 and python-pip/python-pip-whl@9.0.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip@9.0.1-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip/python-pip-whl@9.0.1-2

NVD Description

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

An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a private index. This only affects use of the --extra-index-url option, and exploitation requires that the package does not already exist in the public index (and thus the attacker can put the package there with an arbitrary version number). NOTE: it has been reported that this is intended functionality and the user is responsible for using --extra-index-url securely

Remediation

There is no fixed version for Debian:9 python-pip.

References

low severity

Incorrect Permission Assignment for Critical Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 relevant fixed versions and status.

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:9 shadow.

References

low severity

CVE-2018-6954

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Incorrect Privilege Assignment

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Privilege Chaining

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Access Restriction Bypass

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/bsdutils@1:2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libblkid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libfdisk1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libmount1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libsmartcols1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libuuid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/mount@2.29.2-1+deb9u1

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:9 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

There is no fixed version for Debian:9 util-linux.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

CVE-2018-12698

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.6.3-3.2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z freetype/libfreetype6@2.6.3-3.2

NVD Description

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

FreeType commit 22a0cccb4d9d002f33c1ba7a4b36812c7d4f46b5 was discovered to contain a segmentation violation via the function FT_Request_Size.

Remediation

There is no fixed version for Debian:9 freetype.

References

low severity

Out-of-bounds Read

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.6.3-3.2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z freetype/libfreetype6@2.6.3-3.2

NVD Description

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

FreeType commit 53dfdcd8198d2b3201a23c4bad9190519ba918db was discovered to contain a segmentation violation via the function FNT_Size_Request.

Remediation

There is no fixed version for Debian:9 freetype.

References

low severity

CVE-2021-40330

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 git.

References

low severity

Exposure of Resource to Wrong Sphere

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 git.

References

low severity

Use of Incorrectly-Resolved Name or Reference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:9 git.

References

low severity

Improper Data Handling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Reachable Assertion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:9 glibc.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Key Management Errors

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg-agent@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gpgv@2.1.18-8~deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 gnupg2.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gnupg-agent@2.1.18-8~deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnupg2/gpgv@2.1.18-8~deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 gnupg2.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgcrypt20@1.7.6-2+deb9u3

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:9 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

There is no fixed version for Debian:9 libgcrypt20.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgcrypt20@1.7.6-2+deb9u3

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:9 relevant fixed versions and status.

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:9 libgcrypt20.

References

low severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

gdImageGd2Ptr in gd_gd2.c in the GD Graphics Library (aka LibGD) through 2.3.2 has a double free. NOTE: the vendor's position is "The GD2 image format is a proprietary image format of libgd. It has to be regarded as being obsolete, and should only be used for development and testing purposes.

Remediation

There is no fixed version for Debian:9 libgd2.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 libgd2.

References

low severity

Excessive Iteration

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

libjpeg 9c has a large loop because read_pixel in rdtarga.c mishandles EOF.

Remediation

There is no fixed version for Debian:9 libjpeg-turbo.

References

low severity

Improper Input Validation

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

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

A flaw was found in libwebp in versions before 1.0.1. When reading a file libwebp allocates an excessive amount of memory. The highest threat from this vulnerability is to the service availability.

Remediation

There is no fixed version for Debian:9 libwebp.

References

low severity

Cryptographic Issues

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

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:9 pcre3.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

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:9 pcre3.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/libperl5.24@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-base@5.24.1-3+deb9u5
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z perl/perl-modules-5.24@5.24.1-3+deb9u5

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:9 relevant fixed versions and status.

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

Remediation

There is no fixed version for Debian:9 perl.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

In Lib/tarfile.py in Python through 3.8.3, an attacker is able to craft a TAR archive leading to an infinite loop when opened by tarfile.open, because _proc_pax lacks header validation.

Remediation

Upgrade Debian:9 python2.7 to version 2.7.13-2+deb9u4 or higher.

References

low severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

Lib/zipfile.py in Python through 3.7.2 allows remote attackers to cause a denial of service (resource consumption) via a ZIP bomb.

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 tar.

References

low severity

Missing Release of Resource after Effective Lifetime

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Improper Certificate Validation

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

Detailed paths

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

NVD Description

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

ALPACA is an application layer protocol content confusion attack, exploiting TLS servers implementing different protocols but using compatible certificates, such as multi-domain or wildcard certificates. A MiTM attacker having access to victim's traffic at the TCP/IP layer can redirect traffic from one subdomain to another, resulting in a valid TLS session. This breaks the authentication of TLS and cross-protocol attacks may be possible where the behavior of one protocol service may compromise the other at the application layer.

Remediation

There is no fixed version for Debian:9 nginx.

References

low severity

Access Restriction Bypass

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

Detailed paths

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

NVD Description

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

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

Remediation

There is no fixed version for Debian:9 nginx.

References

low severity

OS Command Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq-dev@9.6.11-0+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z postgresql-9.6/libpq5@9.6.11-0+deb9u1

NVD Description

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

In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to execute arbitrary code in the context of the database's operating system user. This functionality is enabled by default and can be abused to run arbitrary operating system commands on Windows, Linux, and macOS. NOTE: Third parties claim/state this is not an issue because PostgreSQL functionality for ‘COPY TO/FROM PROGRAM’ is acting as intended. References state that in PostgreSQL, a superuser can execute commands as the server user without using the ‘COPY FROM PROGRAM’.

Remediation

There is no fixed version for Debian:9 postgresql-9.6.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-bin@6.0+20161126-1+deb9u2

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 ncurses.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Use After Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Improper Input Validation

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

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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:9 binutils.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.26-3

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z coreutils@8.26-3

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:9 relevant fixed versions and status.

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:9 coreutils.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnutls28/libgnutls30@3.5.8-5+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 gnutls28.

References

low severity

Out-of-Bounds

  • Vulnerable module: jbigkit/libjbig0
  • Introduced through: jbigkit/libjbig0@2.1-3.1+b2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z jbigkit/libjbig0@2.1-3.1+b2

NVD Description

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

In LibTIFF 4.0.8, there is a memory malloc failure in tif_jbig.c. A crafted TIFF document can lead to an abort resulting in a remote denial of service attack.

Remediation

There is no fixed version for Debian:9 jbigkit.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 krb5.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

read_header_tga in gd_tga.c in the GD Graphics Library (aka LibGD) through 2.3.2 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted TGA file.

Remediation

There is no fixed version for Debian:9 libgd2.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgd2/libgd3@2.2.4-2+deb9u4

NVD Description

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

The GD Graphics Library (aka LibGD) through 2.3.2 has an out-of-bounds read because of the lack of certain gdGetBuf and gdPutBuf return value checks.

Remediation

There is no fixed version for Debian:9 libgd2.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: libjpeg-turbo/libjpeg62-turbo
  • Introduced through: libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libjpeg-turbo/libjpeg62-turbo@1:1.5.1-2

NVD Description

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

libjpeg-turbo 1.5.2 has a NULL Pointer Dereference in jdpostct.c and jquant1.c via a crafted JPEG file.

Remediation

There is no fixed version for Debian:9 libjpeg-turbo.

References

low severity

CVE-2018-14048

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

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

An issue has been found in libpng 1.6.34. It is a SEGV in the function png_free_data in png.c, related to the recommended error handling for png_read_image.

Remediation

There is no fixed version for Debian:9 libpng1.6.

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

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

png_create_info_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.

Remediation

There is no fixed version for Debian:9 libpng1.6.

References

low severity

Resource Exhaustion

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

Python 2.7 through 2.7.17, 3.5 through 3.5.9, 3.6 through 3.6.10, 3.7 through 3.7.6, and 3.8 through 3.8.1 allows an HTTP server to conduct Regular Expression Denial of Service (ReDoS) attacks against a client because of urllib.request.AbstractBasicAuthHandler catastrophic backtracking.

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero error and application crash) via a crafted TIFF image that is mishandled by the TIFFWriteScanline function in tif_write.c, as demonstrated by tiffdither.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

An issue was discovered in LibTIFF 4.0.9. There is a NULL pointer dereference in the function LZWDecode in the file tif_lzw.c.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

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

LibTIFF 4.0.9 has a NULL pointer dereference in the jpeg_fdct_16x16 function in jfdctint.c.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

XML External Entity (XXE) Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z expat/libexpat1@2.2.0-2+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 expat.

References

low severity

Race Condition

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libgcrypt20@1.7.6-2+deb9u3

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 libgcrypt20.

References

low severity

CVE-2009-4487

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

Detailed paths

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

NVD Description

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

nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.

Remediation

There is no fixed version for Debian:9 nginx.

References

low severity

Access Restriction Bypass

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 relevant fixed versions and status.

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:9 shadow.

References

low severity

Use of Uninitialized Resource

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

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

An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

Authentication Bypass

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Improper Data Handling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.

Remediation

There is no fixed version for Debian:9 glibc.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libhogweed4@3.3-1+b2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nettle/libnettle6@3.3-1+b2

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 nettle.

References

low severity

CVE-2021-3572

  • Vulnerable module: python-pip
  • Introduced through: python-pip@9.0.1-2 and python-pip/python-pip-whl@9.0.1-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip@9.0.1-2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python-pip/python-pip-whl@9.0.1-2

NVD Description

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

A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.

Remediation

There is no fixed version for Debian:9 python-pip.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnutls28/libgnutls30@3.5.8-5+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 gnutls28.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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:9 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

_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

There is no fixed version for Debian:9 binutils.

References

low severity

Divide By Zero

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Double Free

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

Remediation

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Improper Input Validation

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Incorrect Calculation of Buffer Size

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

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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 (infinite loop) via a crafted ELF file.

Remediation

There is no fixed version for Debian:9 binutils.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

_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

There is no fixed version for Debian:9 binutils.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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:9 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Resource Exhaustion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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:9 binutils.

References

low severity

Use After Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Use After Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

Resource Exhaustion

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 git.

References

low severity

CVE-2019-7309

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.28-1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libpng1.6/libpng16-16@1.6.28-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.

Remediation

There is no fixed version for Debian:9 libpng1.6.

References

low severity

CVE-2018-1000654

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.10-1.1+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libtasn1-6@4.10-1.1+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 libtasn1-6.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: ncurses/libncursesw5
  • Introduced through: ncurses/libncursesw5@6.0+20161126-1+deb9u2, ncurses/libtinfo5@6.0+20161126-1+deb9u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-bin@6.0+20161126-1+deb9u2

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 ncurses.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre16-3
  • Introduced through: pcre3/libpcre16-3@2:8.39-3, pcre3/libpcre3@2:8.39-3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

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:9 pcre3.

References

low severity

Improper Input Validation

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 sqlite3.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tar
  • Introduced through: tar@1.29b-1.1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 tar.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

In LibTIFF, there is a memory malloc failure in tif_pixarlog.c. A crafted TIFF document can lead to an abort, resulting in a remote denial of service attack.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

A flaw was found in libtiff. Due to a memory allocation failure in tif_read.c, a crafted TIFF file can lead to an abort, resulting in denial of service.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: tiff/libtiff5
  • Introduced through: tiff/libtiff5@4.0.8-2+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z tiff/libtiff5@4.0.8-2+deb9u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

Out-of-bounds Read error in tiffcrop in libtiff 4.3.0 allows attackers to cause a denial-of-service via a crafted tiff file. For users that compile libtiff from sources, the fix is available with commit 46dc8fcd.

Remediation

There is no fixed version for Debian:9 tiff.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.29.2-1+deb9u1, util-linux/bsdutils@1:2.29.2-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/bsdutils@1:2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libblkid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libfdisk1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libmount1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libsmartcols1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libuuid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/mount@2.29.2-1+deb9u1

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:9 relevant fixed versions and status.

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:9 util-linux.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.29.2-1+deb9u1, util-linux/bsdutils@1:2.29.2-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/bsdutils@1:2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libblkid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libfdisk1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libmount1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libsmartcols1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/libuuid1@2.29.2-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z util-linux/mount@2.29.2-1+deb9u1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 util-linux.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw5
  • Introduced through: ncurses/libncursesw5@6.0+20161126-1+deb9u2, ncurses/libtinfo5@6.0+20161126-1+deb9u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-bin@6.0+20161126-1+deb9u2

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 ncurses.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 curl.

References

low severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: libxslt/libxslt1-dev
  • Introduced through: libxslt/libxslt1-dev@1.1.29-2.1 and libxslt/libxslt1.1@1.1.29-2.1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1-dev@1.1.29-2.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libxslt/libxslt1.1@1.1.29-2.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxslt package and not the libxslt package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.

Remediation

There is no fixed version for Debian:9 libxslt.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncursesw5
  • Introduced through: ncurses/libncursesw5@6.0+20161126-1+deb9u2, ncurses/libtinfo5@6.0+20161126-1+deb9u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libncursesw5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/libtinfo5@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-base@6.0+20161126-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z ncurses/ncurses-bin@6.0+20161126-1+deb9u2

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 ncurses.

References

low severity

CVE-2020-36309

  • Vulnerable module: nginx
  • Introduced through: nginx@1.10.3-1+deb9u2, nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-auth-pam@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-dav-ext@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-echo@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-geoip@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-image-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-subs-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-upstream-fair@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-http-xslt-filter@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-mail@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/libnginx-mod-stream@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/nginx-common@1.10.3-1+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z nginx/nginx-full@1.10.3-1+deb9u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream nginx package and not the nginx package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

ngx_http_lua_module (aka lua-nginx-module) before 0.10.16 in OpenResty allows unsafe characters in an argument when using the API to mutate a URI, or a request or response header.

Remediation

There is no fixed version for Debian:9 nginx.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre3/libpcre16-3
  • Introduced through: pcre3/libpcre16-3@2:8.39-3, pcre3/libpcre3@2:8.39-3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre16-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre3-dev@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcre32-3@2:8.39-3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z pcre3/libpcrecpp0v5@2:8.39-3

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:9 relevant fixed versions and status.

libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.

Remediation

There is no fixed version for Debian:9 pcre3.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.4-4.1 and shadow/passwd@1:4.4-4.1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 shadow.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl.

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.26-3

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z coreutils@8.26-3

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:9 relevant fixed versions and status.

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:9 coreutils.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.4-4.1 and shadow/passwd@1:4.4-4.1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/login@1:4.4-4.1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z shadow/passwd@1:4.4-4.1

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:9 relevant fixed versions and status.

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

Remediation

There is no fixed version for Debian:9 shadow.

References

low severity

Improper Input Validation

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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:9 systemd.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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:9 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.5.8-5+deb9u4

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z gnutls28/libgnutls30@3.5.8-5+deb9u4

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:9 relevant fixed versions and status.

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:9 gnutls28.

References

low severity

Cryptographic Issues

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python2.7 package and not the python2.7 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

Python 2.7 before 3.4 only uses the last eight bits of the prefix to randomize hash values, which causes it to compute hash values without restricting the ability to trigger hash collisions predictably and makes it easier for context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-1150.

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.16.2-5+deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z sqlite3/libsqlite3-0@3.16.2-5+deb9u1

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:9 relevant fixed versions and status.

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:9 sqlite3.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2 and openldap/libldap-common@2.4.44+dfsg-5+deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-2.4-2@2.4.44+dfsg-5+deb9u2
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openldap/libldap-common@2.4.44+dfsg-5+deb9u2

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:9 relevant fixed versions and status.

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:9 openldap.

References

low severity

CVE-2004-0971

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.15-1+deb9u1, krb5/libk5crypto3@1.15-1+deb9u1 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

The krb5-send-pr script in the kerberos5 (krb5) package in Trustix Secure Linux 1.5 through 2.1, and possibly other operating systems, allows local users to overwrite files via a symlink attack on temporary files.

Remediation

There is no fixed version for Debian:9 krb5.

References

low severity

Permissive Cross-domain Policy with Untrusted Domains

  • Vulnerable module: node
  • Introduced through: node@8.12.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Permissive Cross-domain Policy with Untrusted Domains due to not clearing Proxy-Authentication headers on cross-origin redirects. An attacker can intercept the improperly cleared headers.

Remediation

Upgrade node to version 18.19.1, 20.11.1, 21.6.2 or higher.

References

low severity

LDAP Injection

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.15-1+deb9u1, krb5/libk5crypto3@1.15-1+deb9u1 and others
  • Fixed in: 1.15-1+deb9u3

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libgssapi-krb5-2@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libk5crypto3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5-3@1.15-1+deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z krb5/libkrb5support0@1.15-1+deb9u1

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:9 relevant fixed versions and status.

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:9 krb5 to version 1.15-1+deb9u3 or higher.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@1.4.9, apt/apt-transport-https@1.4.9 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/apt-transport-https@1.4.9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z apt/libapt-pkg5.0@1.4.9

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:9 relevant fixed versions and status.

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:9 apt.

References

low severity

CVE-2020-8284

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u13

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u13 or higher.

References

low severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u15

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u15 or higher.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.0j-1~deb9u1, openssl/libssl-dev@1.1.0j-1~deb9u1 and others
  • Fixed in: 1.1.0l-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl-dev@1.1.0j-1~deb9u1
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl/libssl1.1@1.1.0j-1~deb9u1

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:9 relevant fixed versions and status.

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:9 openssl to version 1.1.0l-1~deb9u1 or higher.

References

low severity

Information Exposure

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1
  • Fixed in: 1.0.2u-1~deb9u2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl1.0 package and not the openssl1.0 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

The Raccoon attack exploits a flaw in the TLS specification which can lead to an attacker being able to compute the pre-master secret in connections which have used a Diffie-Hellman (DH) based ciphersuite. In such a case this would result in the attacker being able to eavesdrop on all encrypted communications sent over that TLS connection. The attack can only be exploited if an implementation re-uses a DH secret across multiple TLS connections. Note that this issue only impacts DH ciphersuites and not ECDH ciphersuites. This issue affects OpenSSL 1.0.2 which is out of support and no longer receiving public updates. OpenSSL 1.1.1 is not vulnerable to this issue. Fixed in OpenSSL 1.0.2w (Affected 1.0.2-1.0.2v).

Remediation

Upgrade Debian:9 openssl1.0 to version 1.0.2u-1~deb9u2 or higher.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1
  • Fixed in: 1.0.2t-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl1.0 package and not the openssl1.0 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

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:9 openssl1.0 to version 1.0.2t-1~deb9u1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.13-2+deb9u3, python2.7/libpython2.7-minimal@2.7.13-2+deb9u3 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-minimal@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/libpython2.7-stdlib@2.7.13-2+deb9u3
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z python2.7/python2.7-minimal@2.7.13-2+deb9u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream python2.7 package and not the python2.7 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.

Remediation

There is no fixed version for Debian:9 python2.7.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.28-5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z binutils@2.28-5

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 binutils.

References

low severity

CVE-2019-1348

  • Vulnerable module: git
  • Introduced through: git@1:2.11.0-3+deb9u4 and git/git-man@1:2.11.0-3+deb9u4
  • Fixed in: 1:2.11.0-3+deb9u5

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git@1:2.11.0-3+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z git/git-man@1:2.11.0-3+deb9u4

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:9 relevant fixed versions and status.

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:9 git to version 1:2.11.0-3+deb9u5 or higher.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.6-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 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

There is no fixed version for Debian:9 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.6-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.6-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 libsepol.

References

low severity

Use After Free

  • Vulnerable module: libsepol/libsepol1
  • Introduced through: libsepol/libsepol1@2.6-2

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z 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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 libsepol.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: libwebp/libwebp6
  • Introduced through: libwebp/libwebp6@0.5.2-1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z libwebp/libwebp6@0.5.2-1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libwebp package and not the libwebp package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

Multiple integer overflows in libwebp allows attackers to have unspecified impact via unknown vectors.

Remediation

There is no fixed version for Debian:9 libwebp.

References

low severity

Missing Initialization of Resource

  • Vulnerable module: curl
  • Introduced through: curl@7.52.1-5+deb9u9, curl/libcurl3@7.52.1-5+deb9u9 and others
  • Fixed in: 7.52.1-5+deb9u15

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3@7.52.1-5+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z curl/libcurl3-gnutls@7.52.1-5+deb9u9

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:9 relevant fixed versions and status.

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:9 curl to version 7.52.1-5+deb9u15 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.15.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly thereby keeping the connection and associated resources alive for a long period of time. Attack potential is mitigated by the use of a load balancer or other proxy layer.

This vulnerability is an extension of CVE-2018-12121, addressed in November, 2018. The 40 second timeout and its adjustment by server.headersTimeout apply to this fix as in CVE-2018-12121.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 11.10.1, 10.15.2, 8.15.1, 6.17.0 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9512, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9518, CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Denial of Service (DoS)

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.16.1

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Denial of Service (DoS). Multiple HTTP/2 Denial of Service vulnerabilities exist within Node.js that could result in an attacker consuming excess CPU, memory, or both, potentially leading to a denial of service conditions.

NOTE: This vulnerability has also been identified as: CVE-2019-9511, CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9516, CVE-2019-9517

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade node to version 8.16.1, 10.16.3, 12.8.1 or higher.

References

low severity

Unauthorized File Access

  • Vulnerable module: node
  • Introduced through: node@8.12.0
  • Fixed in: 8.17.0

Detailed paths

  • Introduced through: docker-image|digitalmarketplace/base@4.3.0-20190309T004201Z node@8.12.0

Overview

node is a JavaScript runtime built on Chrome's V8 JavaScript engine.

Affected versions of this package are vulnerable to Unauthorized File Access. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation.

For npm, a properly constructed entry in the package.json bin field would allow a package publisher to create a symlink pointing to arbitrary files on a user’s system when the package is installed. This behaviour is possible through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Remediation

Upgrade node to version 12.14.0, 10.18.0, 8.17.0, 13.4.0 or higher.

References

low severity

Double Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.24-11+deb9u4, glibc/libc-dev-bin@2.24-11+deb9u4 and others

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc-dev-bin@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/libc6-dev@2.24-11+deb9u4
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z glibc/multiarch-support@2.24-11+deb9u4

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 glibc.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@232-25+deb9u9 and systemd/libudev1@232-25+deb9u9

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libsystemd0@232-25+deb9u9
  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z systemd/libudev1@232-25+deb9u9

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:9 relevant fixed versions and status.

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

There is no fixed version for Debian:9 systemd.

References

low severity

CVE-2021-3601

  • Vulnerable module: openssl1.0/libssl1.0.2
  • Introduced through: openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

Detailed paths

  • Introduced through: digitalmarketplace/base@4.3.0-20190309T004201Z openssl1.0/libssl1.0.2@1.0.2r-1~deb9u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl1.0 package and not the openssl1.0 package as distributed by Debian. See How to fix? for Debian:9 relevant fixed versions and status.

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. OpenSSL does not class this issue as a security vulnerability. The trusted CA store should not contain anything that the user does not trust to issue other certificates. Notes: https://github.com/openssl/openssl/issues/5236#issuecomment-119646061

Remediation

There is no fixed version for Debian:9 openssl1.0.

References