Re: How to check that CVE-2018-6871 is fixed?

Chris Sherlock <chris.sherlock79 -AT- gmail.com>
Tue, 20 Feb 2018 20:22:10 +1100

Sorry to be a pain here, but it appears that the canonical CVE identifier is now CVE-2018-6872 as 
CVE-2018-1055 has been rejected and points to CVE-2018-6872:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1055

Our security advisory list still points to CVE-2018-1055. Should this be updated?

Chris

Sent from my iPhone

On 12 Feb 2018, at 12:50 am, Rene Engelhard <rene@debian.org> wrote:

On Mon, Feb 12, 2018 at 12:32:39AM +1100, Chris Sherlock wrote:
  CVE-2018-1055 is the CVE we have listed on our security advisories page. 
  [1]https://www.libreoffice.org/about-us/security/advisories/


Which is my point, but Paul used "the other one".

Regards,

Rene

Context

How to check that CVE-2018-6871 is fixed? · Paul Menzel
- Re: How to check that CVE-2018-6871 is fixed? · Chris Sherlock
  - Re: How to check that CVE-2018-6871 is fixed? · Chris Sherlock
- Re: How to check that CVE-2018-6871 is fixed? · Rene Engelhard
  - Re: How to check that CVE-2018-6871 is fixed? · Chris Sherlock
    - Re: How to check that CVE-2018-6871 is fixed? · Rene Engelhard
      - Re: How to check that CVE-2018-6871 is fixed? · Chris Sherlock

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.