Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.

The remote Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-5036-1 advisory.

    It was discovered that Tor incorrectly handled certain memory operations. A remote attacker could use this     issue to cause a denial of service. This issue only affected Ubuntu 18.04 ESM. (CVE-2019-8955)

    It was discovered that Tor did not properly handle the input length to dump_desc() function. A remote     attacker could use this issue to cause a denial of service. This issue only affected Ubuntu 16.04 ESM,     Ubuntu 18.04 ESM and Ubuntu 20.04 ESM. (CVE-2021-28089)

    It was discovered that Tor did not properly sanitize the relay nickname in     dirvote_add_signatures_to_pending_consensus() function. An attacker could possibly use this issue to cause     an assertion failure and then cause a denial of service. (CVE-2021-28090)

    It was discovered that Tor did not properly validate the layer hint on half-open streams. A remote     attacker could possibly use this issue to bypass the access control, leading to remote code execution.
    This issue only affected Ubuntu 20.04 ESM. (CVE-2021-34548)

    It was discovered that Tor was using an insecure hash function. A remote attacker could use this issue to     cause a denial of service. This issue only affected Ubuntu 16.04 ESM, Ubuntu 18.04 ESM and Ubuntu 20.04     ESM. (CVE-2021-34549)

    It was discovered that Tor did not properly manage memory under certain circumstances. If a user were     tricked into opening a specially crafted request, a remote attacker could possibly use this issue to cause     a crash, resulting in a denial of service, or possibly reading sensitive data. This issue only affected     Ubuntu 18.04 ESM and Ubuntu 20.04 ESM. (CVE-2021-34550)

    It was discovered that Tor mishandles the relationship between batch-signature verification and single-     signature verification. An attacker could possibly use this issue to cause an assertion failure and then     cause a denial of service. This issue only affected Ubuntu 16.04 ESM, Ubuntu 18.04 ESM and Ubuntu 20.04     ESM. (CVE-2021-38385)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202305-11 (Tor: Multiple Vulnerabilities)

  - Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature     verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.
    (CVE-2021-38385)

  - Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation. (CVE-2022-33903)

  - The SafeSocks option in Tor before 0.4.7.13 has a logic error in which the unsafe SOCKS4 protocol can be     used but not the safe SOCKS4a protocol, aka TROVE-2022-002. (CVE-2023-23589)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has a package installed that is affected by a vulnerability as referenced in the openSUSE-SU-2021:1192-1 advisory.

  - Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature     verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.
    (CVE-2021-38385)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 11 host has packages installed that are affected by a vulnerability as referenced in the dsa-4961 advisory.

  - Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature     verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.
    (CVE-2021-38385)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has a package installed that is affected by a vulnerability as referenced in the openSUSE-SU-2021:1169-1 advisory.

  - Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature     verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.
    (CVE-2021-38385)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
183153	Ubuntu 16.04 ESM / 18.04 ESM / 20.04 ESM : Tor vulnerabilities (USN-5036-1)	Nessus	Ubuntu Local Security Checks	high
175036	GLSA-202305-11 : Tor: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	medium
152837	openSUSE 15 Security Update : tor (openSUSE-SU-2021:1192-1)	Nessus	SuSE Local Security Checks	high
152753	Debian DSA-4961-1 : tor - security update	Nessus	Debian Local Security Checks	high
152696	openSUSE 15 Security Update : tor (openSUSE-SU-2021:1169-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2021-38385

high

Tenable Plugins

high

medium

high

high

high