Snyk - Open Source Security

Snyk test report

September 11th 2026, 6:21:19 pm (UTC+00:00)

Scanned the following paths:
  • docker.io/scopear/docker-db:1.5.15_ddb76b9.88/scopear/docker-db (deb)
  • docker.io/scopear/docker-db:1.5.15_ddb76b9.88/tianon/gosu//usr/local/bin/gosu (gomodules)
6 known vulnerabilities
19 vulnerable dependency paths
150 dependencies

Time-of-check Time-of-use (TOCTOU)

high severity
Exploit: Not Defined
  • Package Manager: ubuntu:20.04
  • Vulnerable module: rsync
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88, mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 and others

Detailed paths

  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › rsync@3.1.3-8ubuntu0.9

NVD Description

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

Rsync versions before 3.4.3 contain a time-of-check to time-of-use (TOCTOU) race condition in daemon file handling that allows attackers to redirect file writes outside intended directories by replacing parent directory components with symbolic links. Attackers with write access to a module path can exploit this race condition to create or overwrite arbitrary files, potentially modifying sensitive system files and achieving privilege escalation when the daemon runs with elevated privileges. This vulnerability can only be triggered if the chroot setting is false.

Remediation

Upgrade Ubuntu:20.04 rsync to version 3.1.3-8ubuntu0.9+esm1 or higher.

References

More about this vulnerability

Out-of-bounds Read

high severity
Exploit: Not Defined
  • Package Manager: ubuntu:20.04
  • Vulnerable module: rsync
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88, mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 and others

Detailed paths

  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › rsync@3.1.3-8ubuntu0.9

NVD Description

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

Rsync version 3.4.2 and prior contain an integer overflow vulnerability in the compressed-token decoder where a 32-bit signed counter is not checked for overflow, allowing a malicious sender to trigger an overflow that causes the receiver process to read and return data from outside the intended buffer bounds. Attackers can exploit this vulnerability to disclose process memory contents including environment variables, passwords, heap and stack data, and library memory pointers, significantly reducing ASLR effectiveness and facilitating further exploitation.

Remediation

Upgrade Ubuntu:20.04 rsync to version 3.1.3-8ubuntu0.9+esm1 or higher.

References

More about this vulnerability

CVE-2026-45447

high severity
Exploit: Not Defined
  • Package Manager: ubuntu:20.04
  • Vulnerable module: openssl/libssl1.1
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88, cyrus-sasl2/libsasl2-modules@2.1.27+dfsg-2ubuntu0.1 and others

Detailed paths

  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › cyrus-sasl2/libsasl2-modules@2.1.27+dfsg-2ubuntu0.1 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-backup@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › ca-certificates@20240203~20.04.1 › openssl@1.1.1f-1ubuntu2.24 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-backup@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-client-core-10.7@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-backup@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-client-core-10.7@1:10.7.8+maria~ubu2004 › mariadb-10.7/libmariadb3@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › galera-4@26.4.14-ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-client-10.7@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-core-10.7@1:10.7.8+maria~ubu2004 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › mariadb-10.7/mariadb-server@1:10.7.8+maria~ubu2004 › mariadb-10.7/mariadb-server-10.7@1:10.7.8+maria~ubu2004 › socat@1.7.3.3-2 › openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › ca-certificates@20240203~20.04.1 › openssl@1.1.1f-1ubuntu2.24

NVD Description

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

Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.

Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.

When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.

In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.

Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm4 or higher.

References

More about this vulnerability

Out-of-bounds Write

high severity
Exploit: Not Defined
  • Package Manager: ubuntu:20.04
  • Vulnerable module: gnupg2/gpgv
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 and gnupg2/gpgv@2.2.19-3ubuntu2.5

Detailed paths

  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › gnupg2/gpgv@2.2.19-3ubuntu2.5
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › apt@2.0.11 › gnupg2/gpgv@2.2.19-3ubuntu2.5
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › gnupg2/gpg@2.2.19-3ubuntu2.5 › gnupg2/gpgconf@2.2.19-3ubuntu2.5
  • Introduced through: docker-image|docker.io/scopear/docker-db@1.5.15_ddb76b9.88 › gnupg2/gpg@2.2.19-3ubuntu2.5

NVD Description

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

In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)

Remediation

Upgrade Ubuntu:20.04 gnupg2 to version 2.2.19-3ubuntu2.5+esm1 or higher.

References

More about this vulnerability

Race Condition Enabling Link Following

high severity
Exploit: Not Defined
  • Manifest file: docker.io/scopear/docker-db:1.5.15_ddb76b9.88/tianon/gosu › /usr/local/bin/gosu
  • Package Manager: golang
  • Vulnerable module: github.com/opencontainers/runc/libcontainer/system
  • Introduced through: github.com/tianon/gosu@* and github.com/opencontainers/runc/libcontainer/system@v1.0.1

Detailed paths

  • Introduced through: github.com/tianon/gosu@* › github.com/opencontainers/runc/libcontainer/system@v1.0.1

Overview

Affected versions of this package are vulnerable to Race Condition Enabling Link Following due to insufficient checks when bind-mounting /dev/pts/$n to /dev/console inside the container. An attacker can gain unauthorized write access to sensitive files within the container environment by manipulating the timing of mount operations and providing a malicious configuration, potentially leading to denial of service or container escape.

Note:

This is only exploitable if the attacker can supply a crafted container configuration and execute processes with sufficient privileges inside the container.

Workaround

This vulnerability can be mitigated by:

  1. Using containers with user namespaces enabled.

  2. Configuring containers to not permit processes to run with root privileges.

  3. Applying SELinux policies that restrict access to /dev/console.

Remediation

Upgrade github.com/opencontainers/runc/libcontainer/system to version 1.2.8, 1.3.3, 1.4.0-rc.3 or higher.

References

More about this vulnerability

Race Condition Enabling Link Following

high severity
Exploit: Proof of Concept
  • Manifest file: docker.io/scopear/docker-db:1.5.15_ddb76b9.88/tianon/gosu › /usr/local/bin/gosu
  • Package Manager: golang
  • Vulnerable module: github.com/opencontainers/runc/libcontainer/system
  • Introduced through: github.com/tianon/gosu@* and github.com/opencontainers/runc/libcontainer/system@v1.0.1

Detailed paths

  • Introduced through: github.com/tianon/gosu@* › github.com/opencontainers/runc/libcontainer/system@v1.0.1

Overview

Affected versions of this package are vulnerable to Race Condition Enabling Link Following in the handling of procfs file writes. An attacker can cause arbitrary writes to sensitive files or trigger a denial of service by redirecting write operations through race conditions and manipulating shared mounts or symbolic links. This can result in bypassing security mechanisms, escalating privileges, or crashing the host system by targeting files such as /proc/sysrq-trigger or altering kernel parameters.

Workaround

This vulnerability can be mitigated by:

  1. Do not run untrusted container images from unknown or unverified sources.

  2. Using rootless containers.

Remediation

Upgrade github.com/opencontainers/runc/libcontainer/system to version 1.2.8, 1.3.3, 1.4.0-rc.3 or higher.

References

More about this vulnerability