Bug 910082 (CVE-2013-5745) - CVE-2013-5745 vino: denial of service flaw
Summary: CVE-2013-5745 vino: denial of service flaw
Alias: CVE-2013-5745
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1007492 1008443 1008445 1008661 1009228 1009233
Blocks: 1008660
TreeView+ depends on / blocked
Reported: 2013-02-11 18:27 UTC by Nathanael Noblet
Modified: 2019-09-29 13:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1007492 1008443 1008445 (view as bug list)
Last Closed: 2015-02-26 22:55:21 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 641811 0 None None None Never
Red Hat Product Errata RHSA-2013:1452 0 normal SHIPPED_LIVE Moderate: vino security update 2013-10-22 21:17:40 UTC

Description Nathanael Noblet 2013-02-11 18:27:17 UTC
Description of problem:
I have vino set to require a password. The system is on a publicly accessible machine. One morning I arrived to find / full and vino-server using inordinate amounts of CPU. In trying to find free space I also noticed that soon after freeing space, it would get used up. (Which is when I looked at what processes were running and found vino using too much CPU for not having a client connected).

In the end I found that ~/.cache/gdm/session.log was 669G. A message was repeated "AM Authentication deferred - ignoring client message". 

It was repeating 80 000 per second in the log file.

Thus Vino should introduce some form of rate limiting or other related features to help avoid this situation. It would also be nice if it could detect something like this and add a setting for blacklisting IPs that make more than X requests per second or some such. I realize though that some of that could be done via a firewall so perhaps not on that second part. However rate limiting the logs would be very useful to avoid this situation

How reproducible:
Not easy to reproduce as I don't know exactly what was making the requests to vino.

Upstream bug:

Comment 1 David King 2013-09-12 13:54:51 UTC
This bug is fixed upstream, and the patch to fix it is simple and can be applied to the version in Fedora:


Comment 3 Vincent Danen 2013-09-16 18:59:07 UTC
Also, this was given the name CVE-2013-5745.

Comment 4 Vincent Danen 2013-09-16 19:20:43 UTC
Created vino tracking bugs for this issue:

Affects: fedora-all [bug 1008661]

Comment 8 errata-xmlrpc 2013-10-22 17:18:45 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2013:1452 https://rhn.redhat.com/errata/RHSA-2013-1452.html

Comment 9 Fedora Update System 2013-10-25 01:51:11 UTC
vino-3.8.1-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.