From ${URL} : Currently, both red_channel_pipes_add_type() and red_channel_pipes_add_empty_msg() use plaing RING_FOREACH() which is not safe versus removals from the ring within the loop body. Yet, when (network) error does occur, the current item could be removed from the ring down the road and the assertion in RING_FOREACH()'s ring_next() could trip, causing the process containing the spice server to abort. An user able to initiate spice connection to the guest could use this flaw to crash the guest. Upstream fix: http://cgit.freedesktop.org/spice/spice/commit/?id=53488f0275d6c8a121af49f7ac817d09ce68090d @maintainer(s): after the bump, in case we need to stabilize the package, please say explicitly if it is ready for the stabilization or not.
Fixed in spice-0.12.3-r1. Please stabilize that version. TARGET KEYWORDS: amd64 x86
(In reply to Doug Goldstein from comment #1) > Fixed in spice-0.12.3-r1. Please stabilize that version. > > TARGET KEYWORDS: amd64 x86 Having twins apparently makes you fall asleep at the keyboard while typing so let me fix that. "Please stable that version."
amd64 stable
x86 stable
GLSA vote: no.
CVE-2013-4130 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4130): The (1) red_channel_pipes_add_type and (2) red_channel_pipes_add_empty_msg functions in server/red_channel.c in SPICE before 0.12.4 do not properly perform ring loops, which might allow remote attackers to cause a denial of service (reachable assertion and server exit) by triggering a network error.
GLSA vote: no Closing as noglsa
