From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Richard Weinberger <richard@sigma-star.at>, barebox@lists.infradead.org
Subject: Re: Various Squashfs Issues
Date: Wed, 17 Jul 2024 09:36:56 +0200 [thread overview]
Message-ID: <03970a3a-e589-4a73-ba94-f2dfc7257502@pengutronix.de> (raw)
In-Reply-To: <2572594.vzjCzTo3RI@somecomputer>
Hello Richard,
On 16.07.24 17:49, Richard Weinberger wrote:
> Hi!
>
> While inspecting the squashfs implementation of Barebox I noticed
> some issues and was able trigger heap corruptions using crafted filesystems.
Thanks for sharing your results. By the way I had started a libfuzzer integration
for barebox a while back that I just pushed here:
https://github.com/a3f/barebox/tree/libfuzzer
It still needs some love to make it upstream, but it's already usable and can find
issues, but it still suffers from depleting memory after a while. I need to fix
those memory leaks and clean it up when I find the time, so we can start more heavily
fuzzing a base set of functionality that's needed for secure boot (mainly partition
tables, file type detection and FIT image parser).
> e.g.
[snip]
> While implementing fixes for them I realized that these are all known
> and fixed in Linux.
>
> I suggest backporting at least these Linux fixes for squashfs:
>
> 01cfb7937a9af ("squashfs: be more careful about metadata corruption")
> d512584780d3e ("squashfs: more metadata hardening")
> cdbb65c4c7ead ("squashfs metadata 2: electric boogaloo")
> 71755ee5350b6 ("squashfs: more metadata hardening")
> a3f94cb99a854 ("Squashfs: Compute expected length from inode size rather than block length")
Backported in https://lore.barebox.org/barebox/20240717063328.2810835-1-a.fatoum@pengutronix.de/
Cheers,
Ahmad
>
> Thanks,
> //richard
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-07-17 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:49 Richard Weinberger
2024-07-17 7:36 ` Ahmad Fatoum [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=03970a3a-e589-4a73-ba94-f2dfc7257502@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=richard@sigma-star.at \
/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