From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202006-06 ] ssvnc: Multiple vulnerabilities
Date: Fri, 12 Jun 2020 21:10:09 -0400 [thread overview]
Message-ID: <20200613011009.GD17996@bubba> (raw)
[-- Attachment #1: Type: text/plain, Size: 3116 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202006-06
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: ssvnc: Multiple vulnerabilities
Date: June 13, 2020
Bugs: #701820
ID: 202006-06
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in ssvnc, the worst of which
could result in the arbitrary execution of code.
Background
==========
The Enhanced TightVNC Viewer, SSVNC, adds encryption security to VNC
connections.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-misc/ssvnc <= 1.0.29-r2 Vulnerable!
-------------------------------------------------------------------
NOTE: Certain packages are still vulnerable. Users should migrate
to another package if one is available or wait for the
existing packages to be marked stable by their
architecture maintainers.
Description
===========
Multiple vulnerabilities have been discovered in ssvnc. Please review
the CVE identifiers referenced below for details.
Impact
======
Please review the referenced CVE identifiers for details.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
Gentoo has discontinued support for ssvnc. We recommend that users
unmerge ssvnc:
# emerge --unmerge "net-misc/ssvnc"
NOTE: The Gentoo developer(s) maintaining ssvnc have discontinued
support at this time. It may be possible that a new Gentoo developer
will update ssvnc at a later date. An alternative may be a manual SSH
tunnel.
References
==========
[ 1 ] CVE-2018-20020
https://nvd.nist.gov/vuln/detail/CVE-2018-20020
[ 2 ] CVE-2018-20021
https://nvd.nist.gov/vuln/detail/CVE-2018-20021
[ 3 ] CVE-2018-20022
https://nvd.nist.gov/vuln/detail/CVE-2018-20022
[ 4 ] CVE-2018-20024
https://nvd.nist.gov/vuln/detail/CVE-2018-20024
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202006-06
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.
License
=======
Copyright 2020 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2020-06-13 1:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200613011009.GD17996@bubba \
--to=bman@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox