Bug#914381: libsndfile: CVE-2018-19432

To: Erik de Castro Lopo <erikd@mega-nerd.com>, 914381@bugs.debian.org
Subject: Bug#914381: libsndfile: CVE-2018-19432
From: Petter Reinholdtsen <pere@hungry.com>
Date: Fri, 16 Aug 2019 10:38:02 +0200
Message-id: <[🔎] sa6a7c9jyj9.fsf@hjemme.reinholdtsen.name>
Reply-to: Petter Reinholdtsen <pere@hungry.com>, 914381@bugs.debian.org
In-reply-to: <[🔎] 20190816162157.96208be4c8b599f3583e1c12@mega-nerd.com>
References: <154291799730.3153.16769312570447053767.reportbug@eldamar.local> <20190102102304.GA10800@eldamar.local> <154291799730.3153.16769312570447053767.reportbug@eldamar.local> <[🔎] 20190816061041.GA21024@hjemme.reinholdtsen.name> <[🔎] 20190816162157.96208be4c8b599f3583e1c12@mega-nerd.com> <154291799730.3153.16769312570447053767.reportbug@eldamar.local>

[Erik de Castro Lopo]
> You need to ask the debian people as they are the ones that apply
> patches to my releases.

This is what I am trying to do, using the sensible mechanism (the bug
tracking system).

Is there a new release of libsndfile with all security fixes available?
Will a simple update in Debian to the latest version fix it?

(If the question seem strange, keep in mind I do not know much about
libsndfile, just noticed a strange security issue status. :)

-- 
Happy hacking
Petter Reinholdtsen

Reply to:

References:
- Bug#914381: libsndfile: CVE-2018-19432
  - From: Petter Reinholdtsen <pere@hungry.com>
- Bug#914381: libsndfile: CVE-2018-19432
  - From: Erik de Castro Lopo <erikd@mega-nerd.com>

Prev by Date: Processed: Block GCC 9 build failures in dependent packages by JUCE failure
Next by Date: ffmpeg_4.1.4-1~deb10u1_amd64.changes ACCEPTED into proposed-updates->stable-new
Previous by thread: Bug#914381: libsndfile: CVE-2018-19432
Next by thread: Bug#925771: lmms: ftbfs with GCC-9
Index(es):
- Date
- Thread