oss-sec mailing list archives
Re: [tigervnc-devel] Re: [tigervnc-announce] TigerVNC 1.7.1
From: Alan Coopersmith <alan.coopersmith () oracle com>
Date: Mon, 23 Jan 2017 23:14:19 -0800
On 01/23/17 12:34 AM, Pierre Ossman wrote:
On 22/01/17 07:25, Alan Coopersmith wrote:Is there a CVE assigned to this issue that we should use when passing this fix through to our packages/distros? I don't see one mentioned in the commit or pull requests: https://github.com/TigerVNC/tigervnc/commit/18c020124ff1b2441f714da2017f63dba50720ba https://github.com/TigerVNC/tigervnc/pull/399Not to my knowledge, no.
Thanks. Mitre - can a CVE be assigned for the above issue, as fixed in TigerVNC 1.7.1 ( https://github.com/TigerVNC/tigervnc/releases/tag/v1.7.1 )? -- -Alan Coopersmith- alan.coopersmith () oracle com Oracle Solaris Engineering - http://blogs.oracle.com/alanc
Current thread:
- Re: [tigervnc-announce] TigerVNC 1.7.1 Alan Coopersmith (Jan 21)
- Re: [tigervnc-devel] Re: [tigervnc-announce] TigerVNC 1.7.1 Pierre Ossman (Jan 23)
- Re: [tigervnc-devel] Re: [tigervnc-announce] TigerVNC 1.7.1 Alan Coopersmith (Jan 23)
- Re: [tigervnc-announce] TigerVNC 1.7.1 cve-assign (Jan 25)
- Re: [tigervnc-devel] Re: [tigervnc-announce] TigerVNC 1.7.1 Pierre Ossman (Jan 23)