From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libid3tag: switch to debian to fix CVEs
Date: Thu, 30 Apr 2020 14:39:26 +0200 [thread overview]
Message-ID: <87pnbp5erl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200412101845.1013976-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 12 Apr 2020 12:18:44 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Upstream libid3tag is dead since 2004 so switch to debian to get two
> patches that fix the following CVEs:
> - CVE-2004-2779: id3_utf16_deserialize() in utf16.c in libid3tag
> through 0.15.1b misparses ID3v2 tags encoded in UTF-16 with an odd
> number of bytes, triggering an endless loop allocating memory until
> an OOM condition is reached, leading to denial-of-service (DoS).
> - CVE-2017-11550: The id3_ucs4_length function in ucs4.c in libid3tag
> 0.15.1b allows remote attackers to cause a denial of service (NULL
> Pointer Dereference and application crash) via a crafted mp3 file.
> - CVE-2017-11551: The id3_field_parse function in field.c in libid3tag
> 0.15.1b allows remote attackers to cause a denial of service (OOM)
> via a crafted MP3 file.
> Moreover, drop patch (replaced by add-m4-directory.patch debian patch)
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2020.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-04-30 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 10:18 [Buildroot] [PATCH 1/2] package/libid3tag: switch to debian to fix CVEs Fabrice Fontaine
2020-04-12 10:18 ` [Buildroot] [PATCH 2/2] package/libmad: " Fabrice Fontaine
2020-04-21 9:11 ` Peter Korsgaard
2020-04-30 12:39 ` Peter Korsgaard
2020-04-12 20:22 ` [Buildroot] [PATCH 1/2] package/libid3tag: " Yann E. MORIN
2020-04-30 12:39 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnbp5erl.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox