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

×
Alerts This Week
Warning Icon 1 573
Alerts This Week
Warning Icon 1 573

Gentoo: GLSA 202411-01 High: Neat VNC Authentication Bypass Issue

gentoo
Calendar Grey November 6, 2024
Dist Gentoo Esm H88
A critical Gentoo advisory highlights the significant Neat VNC authentication bypass flaw and its remediation efforts.
A vulnerability has been discovered in Neat VNC, which can lead to authentication bypass.

Summary

Neat VNC allows remote attackers to bypass authentication via a request in which the client specifies an insecure security type such as "Type 1 - None", which is accepted even if it is not offered by the server, as originally demonstrated using a long password.

Resolution

All Neat VNC users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=gui-libs/neatvnc-0.8.1"

References


Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202411-01
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: High
Title: Neat VNC: Authentication Bypass
Date: November 06, 2024
Bugs: #937140
ID: 202411-01

Synopsis

A vulnerability has been discovered in Neat VNC, which can lead to authentication bypass.

Background

Neat VNC is a liberally licensed VNC server library that's intended to be fast and neat.

Get the latest News and Insights

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

Affected Packages

Package Vulnerable Unaffected ---------------- ------------ ------------ gui-libs/neatvnc < 0.8.1 >= 0.8.1

Impact

A remote attacker can opt not to use any authentication method and access the VNC server.

Workaround

There is no known workaround at this time.