Skip to content

fix: address fuzzing findings and other miscellaneous issues#1360

Merged
egibs merged 2 commits into
chainguard-dev:mainfrom
egibs:fuzz-fixes
Feb 6, 2026
Merged

fix: address fuzzing findings and other miscellaneous issues#1360
egibs merged 2 commits into
chainguard-dev:mainfrom
egibs:fuzz-fixes

Conversation

@egibs
Copy link
Copy Markdown
Member

@egibs egibs commented Feb 5, 2026

This PR addresses the issues that came up in the first round of long-term fuzzing.

We needed additional checking for parent directory symlink traversals when extracting archives along with size limits for programkind checks and ignoring invalid Yara/YAML patterns to avoid crashing the fuzzers.

Additionally, this PR cleans up more potential FD leaks and adds validation around OCI image layer sizes and fixes the UPX binary we use, among other things.

make fuzz runs cleanly with these fixes.

@egibs egibs requested a review from stevebeattie February 5, 2026 19:31
@egibs egibs force-pushed the fuzz-fixes branch 6 times, most recently from 5540268 to 50d34b3 Compare February 5, 2026 22:14
@egibs egibs enabled auto-merge (squash) February 5, 2026 23:07
Comment thread pkg/archive/archive.go Outdated
Comment thread pkg/archive/deb.go
@egibs egibs force-pushed the fuzz-fixes branch 2 times, most recently from 511c5dc to bedbd79 Compare February 6, 2026 01:59
@egibs egibs requested a review from stevebeattie February 6, 2026 02:01
@egibs egibs changed the title fix: address fuzzing issues fix: address fuzzing findings and other miscellaneous issues Feb 6, 2026
@egibs egibs force-pushed the fuzz-fixes branch 2 times, most recently from 760624f to 6af6e80 Compare February 6, 2026 14:00
Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
@egibs egibs merged commit dd0e3d0 into chainguard-dev:main Feb 6, 2026
18 checks passed
@egibs egibs deleted the fuzz-fixes branch February 6, 2026 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants