Bug 1381931 (CVE-2016-5407) - CVE-2016-5407 libXv: Insufficient validation of server responses results in out-of bounds accesses
Summary: CVE-2016-5407 libXv: Insufficient validation of server responses results in o...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2016-5407
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1381932
Blocks: 1381939
TreeView+ depends on / blocked
 
Reported: 2016-10-05 11:37 UTC by Andrej Nemec
Modified: 2021-02-17 03:13 UTC (History)
5 users (show)

Fixed In Version: libXv 1.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 02:59:41 UTC


Attachments (Terms of Use)

Description Andrej Nemec 2016-10-05 11:37:58 UTC
It was found that when receiving a response from the server protocol data is not validated sufficiently. The Xv query functions for adaptors and encodings suffer from out of boundary accesses if a hostile X server sends a maliciously crafted response.

Upstream patch:

https://cgit.freedesktop.org/xorg/lib/libXv/commit/?id=d9da580b46a28ab497de2e94fdc7b9ff953dab17

External References:

https://lists.x.org/archives/xorg-announce/2016-October/002720.html

CVE assignment:

http://seclists.org/oss-sec/2016/q4/17

Comment 1 Andrej Nemec 2016-10-05 11:38:18 UTC
Created libXv tracking bugs for this issue:

Affects: fedora-all [bug 1381932]

Comment 3 Huzaifa S. Sidhpurwala 2017-08-28 07:00:06 UTC
Analysis:

This issue stem from the client libraries trusting the server to send correct protocol data, and not verifying that the values will not overflow or cause other damage. Most of the time X clients & servers are run by the same user, with the server more privileged than the clients, under these circumstances this flaw should be non-exploitable, unless the attacker is able to run a MITM attack and impersonate a legitimate X server.


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