zalando / zalando/postgres-operator
CVE-2024-56171 on pgbouncer image
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.14.0
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
- Are you running Postgres Operator in production? yes
- Type of issue? CVE
image: registry.opensource.zalan.do/acid/pgbouncer:master-32
│ libxml2 │ CVE-2024-56171 │ CRITICAL │ │ 2.11.6-r0 │ 2.11.8-r1 │ libxml2: Use-After-Free in libxml2 │
│ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-56171
Could you please update the image ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where the registry.opensource.zalan.do/acid/pgbouncer:master-32 image is defined in the repository. Update the image reference as needed, then verify that the resulting image no longer reports libxml2 CVE-2024-56171; the issue does not name a specific file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- databases, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100