Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 556
Alerts This Week
Warning Icon 1 556

Gentoo: GLSA 202409-25 minor severity: OpenSSL flaws associated with DoS

gentoo
Calendar Grey September 24, 2024
Dist Gentoo Esm H88
The Gentoo GLSA 202409-25 details security notices regarding Tor, addressing various vulnerabilities including potential denial of service threats.
Multiple vulnerabilities have been found in Tor, the worst of which could result in denial of service.

Summary

Multiple vulnerabilities have been discovered in Tor. Please review the CVE identifiers referenced below for details.

Resolution

All Tor users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=net-vpn/tor-0.4.8.9"

References

[ 1 ] TROVE-2023-004 [ 2 ] TROVE-2023-006

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202409-24
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: Tor: Multiple Vulnerabilities
Date: September 24, 2024
Bugs: #916759, #917142
ID: 202409-24

Synopsis

Multiple vulnerabilities have been found in Tor, the worst of which could result in denial of service.

Background

Tor is an implementation of second generation Onion Routing, a connection-oriented anonymizing communication service.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected ----------- ------------ ------------ net-vpn/tor < 0.4.8.9 >= 0.4.8.9

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.