From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1417 invoked by alias); 3 Aug 2019 20:27:34 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 1407 invoked by uid 89); 3 Aug 2019 20:27:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.4 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.1 spammy=our X-Spam-Status: No, score=-6.4 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: Subject: CVE-2019-12900 From: Mark Wielaard To: bzip2-devel@sourceware.org Cc: Julian Seward Date: Tue, 01 Jan 2019 00:00:00 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q3/txt/msg00043.txt.bz2 Hi, I wrote a bit about our handling of CVE-2019-12900 and the bzip2 1.0.7 and 1.0.8 releases. https://gnu.wildebeest.org/blog/mjw/2019/08/02/bzip2-and-the-cve-that-wasnt/ Please do leave a comment if I got something wrong. Thanks, Mark