Docker docker:18.09.5-git

Vulnerabilities

 32 via 39 paths

Dependencies

 27

Source

 Group 6 Copy Created with Sketch. Docker

Target OS

 alpine:3.9.3
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 25
  • 4
  • 3
Status
  • 32
  • 0
  • 0

high severity

Arbitrary Code Injection

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r4

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1

Overview

Affected versions of this package are vulnerable to Arbitrary Code Injection curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.

Remediation

Upgrade curl to version or higher.

References

Arbitrary Code Injection vulnerability report

high severity

Buffer Overflow

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r3

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1
Buffer Overflow vulnerability report

high severity

Double Free

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r3

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1
Double Free vulnerability report

high severity

Information Exposure

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r4

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1

Overview

Affected versions of this package are vulnerable to Information Exposure curl 7.62.0 through 7.70.0 is vulnerable to an information disclosure vulnerability that can lead to a partial password being leaked over the network and to the DNS server(s).

Remediation

Upgrade curl to version or higher.

References

Information Exposure vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r2

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1

Overview

A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

References

Out-of-bounds Write vulnerability report

high severity

Use After Free

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.66.0-r5

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1

Overview

Affected versions of this package are vulnerable to Use After Free. Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.

Remediation

Upgrade curl to version or higher.

References

Use After Free vulnerability report

high severity

Out-of-bounds Read

  • Vulnerable module: expat/expat
  • Introduced through: expat/expat@2.2.6-r0
  • Fixed in: 2.2.7-r1

Detailed paths

  • Introduced through: docker:18.09.5-git@* › expat/expat@2.2.6-r0

Overview

In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCurrentLineNumber (or XML_GetCurrentColumnNumber) then resulted in a heap-based buffer over-read.

References

Out-of-bounds Read vulnerability report

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: expat/expat
  • Introduced through: expat/expat@2.2.6-r0
  • Fixed in: 2.2.7-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › expat/expat@2.2.6-r0

Overview

In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable for denial-of-service attacks).

References

XML External Entity (XXE) Injection vulnerability report

high severity

CVE-2019-1353

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to CVE-2019-1353. 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 git to version or higher.

References

CVE-2019-1353 vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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 git to version or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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

Upgrade git to version or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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 git to version or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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

Upgrade git to version or higher.

References

Improper Input Validation vulnerability report

high severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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 git to version or higher.

References

Improper Input Validation vulnerability report

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.4-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials. 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 git to version or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Insufficiently Protected Credentials

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.3-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Insufficiently Protected Credentials. 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 git to version or higher.

References

Insufficiently Protected Credentials vulnerability report

high severity

Use of Incorrectly-Resolved Name or Reference

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Use of Incorrectly-Resolved Name or Reference. A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

Remediation

Upgrade git to version or higher.

References

Use of Incorrectly-Resolved Name or Reference vulnerability report

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r1

Detailed paths

  • Introduced through: docker:18.09.5-git@* › libssh2/libssh2@1.8.2-r0

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound. 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 libssh2 to version or higher.

References

Integer Overflow or Wraparound vulnerability report

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r1

Detailed paths

  • Introduced through: docker:18.09.5-git@* › libssh2/libssh2@1.8.2-r0

Overview

The SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a denial of service condition on the client system when a user connects to the server.

References

Integer Overflow or Wraparound vulnerability report

high severity
new

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2
  • Introduced through: libssh2/libssh2@1.8.2-r0
  • Fixed in: 1.9.0-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › libssh2/libssh2@1.8.2-r0

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. 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 libssh2 to version or higher.

References

Out-of-bounds Read vulnerability report

high severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.20-r4 and musl/musl-utils@1.1.20-r4
  • Fixed in: 1.1.20-r5

Detailed paths

  • Introduced through: docker:18.09.5-git@* › musl/musl@1.1.20-r4
  • Introduced through: docker:18.09.5-git@* › musl/musl-utils@1.1.20-r4

Overview

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

References

Out-of-bounds Write vulnerability report

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.35.1-r0
  • Fixed in: 1.35.1-r1

Detailed paths

  • Introduced through: docker:18.09.5-git@* › nghttp2/nghttp2-libs@1.35.1-r0

Overview

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

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Improper Enforcement of Message or Data Structure

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.35.1-r0
  • Fixed in: 1.35.1-r2

Detailed paths

  • Introduced through: docker:18.09.5-git@* › nghttp2/nghttp2-libs@1.35.1-r0

Overview

Affected versions of this package are vulnerable to Improper Enforcement of Message or Data Structure. 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 nghttp2 to version or higher.

References

Improper Enforcement of Message or Data Structure vulnerability report

high severity

Resource Exhaustion

  • Vulnerable module: nghttp2/nghttp2-libs
  • Introduced through: nghttp2/nghttp2-libs@1.35.1-r0
  • Fixed in: 1.35.1-r1

Detailed paths

  • Introduced through: docker:18.09.5-git@* › nghttp2/nghttp2-libs@1.35.1-r0

Overview

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

References

Resource Exhaustion vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1b-r1 and openssl/libssl1.1@1.1.1b-r1
  • Fixed in: 1.1.1g-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › openssl/libcrypto1.1@1.1.1b-r1
  • Introduced through: docker:18.09.5-git@* › openssl/libssl1.1@1.1.1b-r1

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

Remediation

Upgrade openssl to version or higher.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Write

  • Vulnerable module: musl/musl
  • Introduced through: musl/musl@1.1.20-r4 and musl/musl-utils@1.1.20-r4
  • Fixed in: 1.1.20-r6

Detailed paths

  • Introduced through: docker:18.09.5-git@* › musl/musl@1.1.20-r4
  • Introduced through: docker:18.09.5-git@* › musl/musl-utils@1.1.20-r4

Overview

Affected versions of this package are vulnerable to Out-of-bounds Write. In musl libc through 1.2.1, wcsnrtombs mishandles particular combinations of destination buffer size and source character limit, as demonstrated by an invalid write access (buffer overflow).

Remediation

Upgrade musl to version or higher.

References

Out-of-bounds Write vulnerability report

medium severity

Information Exposure

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1b-r1 and openssl/libssl1.1@1.1.1b-r1
  • Fixed in: 1.1.1d-r2

Detailed paths

  • Introduced through: docker:18.09.5-git@* › openssl/libcrypto1.1@1.1.1b-r1
  • Introduced through: docker:18.09.5-git@* › openssl/libssl1.1@1.1.1b-r1

Overview

Affected versions of this package are vulnerable to Information Exposure. 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 openssl to version or higher.

References

Information Exposure vulnerability report

medium severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1b-r1 and openssl/libssl1.1@1.1.1b-r1
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › openssl/libcrypto1.1@1.1.1b-r1
  • Introduced through: docker:18.09.5-git@* › openssl/libssl1.1@1.1.1b-r1

Overview

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

References

Missing Encryption of Sensitive Data vulnerability report

medium severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1b-r1 and openssl/libssl1.1@1.1.1b-r1
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › openssl/libcrypto1.1@1.1.1b-r1
  • Introduced through: docker:18.09.5-git@* › openssl/libssl1.1@1.1.1b-r1

Overview

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

References

Use of Insufficiently Random Values vulnerability report

low severity

Integer Overflow or Wraparound

  • Vulnerable module: curl/libcurl
  • Introduced through: curl/libcurl@7.64.0-r1
  • Fixed in: 7.64.0-r2

Detailed paths

  • Introduced through: docker:18.09.5-git@* › curl/libcurl@7.64.0-r1

Overview

An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

References

Integer Overflow or Wraparound vulnerability report

low severity

Improper Input Validation

  • Vulnerable module: git/git
  • Introduced through: git/git@2.20.1-r0
  • Fixed in: 2.20.2-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › git/git@2.20.1-r0

Overview

Affected versions of this package are vulnerable to Improper Input Validation. 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 git to version or higher.

References

Improper Input Validation vulnerability report

low severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl/libcrypto1.1
  • Introduced through: openssl/libcrypto1.1@1.1.1b-r1 and openssl/libssl1.1@1.1.1b-r1
  • Fixed in: 1.1.1d-r0

Detailed paths

  • Introduced through: docker:18.09.5-git@* › openssl/libcrypto1.1@1.1.1b-r1
  • Introduced through: docker:18.09.5-git@* › openssl/libssl1.1@1.1.1b-r1

Overview

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

References

Missing Encryption of Sensitive Data vulnerability report