Bug#888654: mpv: CVE-2018-6360

2018-02-06 Thread James Cowgill
Hi, On 06/02/18 18:08, Luciano Bello wrote: > On 2018-02-03 09:13, James Cowgill wrote: >> Unlike the backport for 0.27 which was fairly straightforward, the >> backport for 0.23 required significant changes and I ended up rewriting >> half of it. This means I am less confident about catching all

Bug#888654: mpv: CVE-2018-6360

2018-02-06 Thread Luciano Bello
On 2018-02-03 09:13, James Cowgill wrote: > Unlike the backport for 0.27 which was fairly straightforward, the > backport for 0.23 required significant changes and I ended up rewriting > half of it. This means I am less confident about catching all the cases > to fix this bug. It would be good if

Bug#888654: mpv: CVE-2018-6360

2018-02-03 Thread James Cowgill
Hi, On 28/01/18 14:17, Salvatore Bonaccorso wrote: > Source: mpv > Version: 0.23.0-1 > Severity: grave > Tags: security upstream > Forwarded: https://github.com/mpv-player/mpv/issues/5456 > > Hi, > > the following vulnerability was published for mpv. > > CVE-2018-6360[0]: > | mpv through

Bug#888654: mpv: CVE-2018-6360

2018-01-28 Thread Salvatore Bonaccorso
Source: mpv Version: 0.23.0-1 Severity: grave Tags: security upstream Forwarded: https://github.com/mpv-player/mpv/issues/5456 Hi, the following vulnerability was published for mpv. CVE-2018-6360[0]: | mpv through 0.28.0 allows remote attackers to execute arbitrary code | via a crafted web