First published: Sat Apr 01 2017(Updated: )
In TigerVNC (VNCSConnectionST.cxx VNCSConnectionST::fence), an authenticated client can cause a double free, leading to a crash of the TigerVNC server. Upstream patch: <a href="https://github.com/TigerVNC/tigervnc/pull/438/commits/f3afa24da144409a3c3a0e35913112583d987671">https://github.com/TigerVNC/tigervnc/pull/438/commits/f3afa24da144409a3c3a0e35913112583d987671</a> Upstream bug: <a href="https://github.com/TigerVNC/tigervnc/issues/437">https://github.com/TigerVNC/tigervnc/issues/437</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Tigervnc | =1.7.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7393 is considered a medium severity vulnerability as it allows an authenticated client to cause a crash of the TigerVNC server.
To fix CVE-2017-7393, users should upgrade to the latest version of TigerVNC that contains the patch addressing this vulnerability.
CVE-2017-7393 affects users running TigerVNC version 1.7.1.
Attackers exploiting CVE-2017-7393 can cause a denial of service by triggering a double free condition that crashes the TigerVNC server.
Yes, CVE-2017-7393 requires authentication, allowing only authenticated clients to exploit the vulnerability.