From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Adrian Perez de Castro <aperez@igalia.com>
Subject: Re: [Buildroot] [PATCH] package/webkitgtk: security bump to version 2.42.5
Date: Fri, 08 Mar 2024 14:45:41 +0100 [thread overview]
Message-ID: <87r0gkvnui.fsf@48ers.dk> (raw)
In-Reply-To: <87h6ijyuyf.fsf@48ers.dk> (Peter Korsgaard's message of "Thu, 08 Feb 2024 13:57:44 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>> Fixes the following security issues:
>> https://webkitgtk.org/security/WSA-2024-0001.html
>> - CVE-2024-23222: Processing maliciously crafted web content may lead to
>> arbitrary code execution. Apple is aware of a report that this issue may
>> have been exploited. Description: A type confusion issue was addressed
>> with improved checks.
>> - CVE-2024-23206: A maliciously crafted webpage may be able to fingerprint
>> the user. Description: An access issue was addressed with improved access
>> restrictions.
>> - CVE-2024-23213: Processing web content may lead to arbitrary code execution.
>> Description: The issue was addressed with improved memory handling.
>> - CVE-2023-40414: Processing web content may lead to arbitrary code
>> execution. Description: A use-after-free issue was addressed with
>> improved memory management.
>> - CVE-2023-42833: Processing web content may lead to arbitrary code execution.
>> Description: A correctness issue was addressed with improved checks.
>> - CVE-2014-1745: Processing a file may lead to a denial-of-service or
>> potentially disclose memory contents. Description: The issue was
>> addressed with improved checks.
>> https://webkitgtk.org/security/WSA-2023-0012.html
>> - CVE-2023-42883: Processing a SVG image may lead to a denial-of-service.
>> Description: The issue was addressed with improved memory handling.
>> - CVE-2023-42890: Processing web content may lead to arbitrary code
>> execution. Description: The issue was addressed with improved memory
>> handling.
>> https://webkitgtk.org/security/WSA-2023-0011.html
>> - CVE-2023-42916: Processing web content may disclose sensitive information.
>> Apple is aware of a report that this issue may have been actively
>> exploited. Description: An out-of-bounds read was addressed with improved
>> input validation.
>> - CVE-2023-42917: Processing web content may lead to arbitrary code
>> execution. Apple is aware of a report that this issue may have been
>> actively exploited. Description: A memory corruption vulnerability was
>> addressed with improved locking.
>> Add an upstream post-2.42.5 patch to fix an issue with an invalid backport
>> causing a build issue.
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Committed, thanks.
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-03-08 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 7:09 [Buildroot] [PATCH] package/webkitgtk: security bump to version 2.42.5 Peter Korsgaard
2024-02-08 9:28 ` Adrian Perez de Castro
2024-02-08 12:57 ` Peter Korsgaard
2024-03-08 13:45 ` 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=87r0gkvnui.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=aperez@igalia.com \
--cc=buildroot@buildroot.org \
/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