CVE-2023-4863 Heap buffer overflow in libwebp
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Description of the bug:
The Bazel container contains a version of libwebp6 that is vulnerable to CVE-2023-4863
### Which category does this issue belong to?
External Dependency
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
```sh
docker run --entrypoint /bin/dpkg gcr.io/bazel-public/bazel:latest -l libwebp6
```
Notice the version is `0.6.1-2ubuntu0.20.04.2`.
### Which operating system are you running Bazel on?
_No response_
### What is the output of `bazel info release`?
_No response_
### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.
_No response_
### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?
_No response_
### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
_No response_
### Have you found anything relevant by searching the web?
https://ubuntu.com/security/CVE-2023-4863
### Any other information, logs, or outputs that you want to share?
_No response_
Contributor guide
Research direction
Start with the Bazel container definition and the package installation or image build entry point, then reproduce the issue with the provided docker run command. Trace where libwebp6 is sourced and verify the resulting image contains a version addressing CVE-2023-4863. Done means the container no longer reports the vulnerable package version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ubuntu
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100