Mailing-List: contact user-help@guacamole.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@guacamole.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPh_e-hxSrWrJdGZn203tT3pVqQF9yfVv=dc9U1jf96X8w0CvA@mail.gmail.com>
References: <CAPh_e-hxSrWrJdGZn203tT3pVqQF9yfVv=dc9U1jf96X8w0CvA@mail.gmail.com>
From: Mike Jumper <mike.jumper@guac-dev.org>
Date: Wed, 14 Dec 2016 11:47:05 -0800
Message-ID: <CALKeL-MEFvPe+32b0Fqd6qeXreBaFPYC6T_PfakjhWcDET=EmQ@mail.gmail.com>
Subject: Re: Security Vulnerabilities?
To: user@guacamole.incubator.apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Wed, 14 Dec 2016 19:47:20 -0000

On Wed, Dec 14, 2016 at 10:27 AM, Ray Jantz <ray.jantz@gmail.com> wrote:
> Hi,
>
> I need to persuade a sys admin that guacamole is secure enough to deploy in
> an enterprise.

That is exactly Guacamole's intended use.

> Security is not one of my strong points, so I'm wondering if
> anyone can comment on this subject and maybe offer some talking points I can
> use?
>

We do have code review processes in place intended to prevent this
sort of thing, as well as automated static analysis scans via CI.
There are no current known vulnerabilities. Historically, there have
been two reported vulnerabilities, both of which were fixed:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-4415
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1566 (see
https://glyptodon.org/jira/browse/GUAC-1465)

In general, I would argue that the architecture of Guacamole actually
serves to increase the security of a remote desktop deployment. Its
nature as a gateway reduces overall attack surface, with all traffic
routed through an authentication layer and strong encryption (assuming
you set up proper SSL/TLS, of course). That gateway aspect also allows
admins to more tightly control which remote desktops can and cannot be
accessed by authorized users, rather than exposing access to an entire
subnet of remote desktops via VPN, for example.

Thanks,

- Mike