apache / apache/apisix-helm-chart
Container Image Contains Known CVEs
- Dominant language
- Go Template
- Stars
- 289
- Forks
- 282
- Avg merge
- 15h 55m
- Merged PRs (30d)
- 3
Description
**Description**
The Helm chart specifies a container image that contains one or more known Common Vulnerabilities and Exposures (CVEs). Although the image is available and can be successfully pulled, deploying the chart introduces known security vulnerabilities into the application environment.
This issue concerns the image selected by the chart rather than the application's source code. The referenced image may be a valid and functional image, but its contents contain known vulnerabilities that could potentially expose the deployed application or its underlying environment to security risks.
Location:
[etcd-12.0.18.tgz](https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix/charts/etcd-12.0.18.tgz)
Image: docker.io/bitnamilegacy/etcd:latest
**What Happens**
When users deploy the Helm chart with its default configuration, Kubernetes pulls and runs the specified container image. Security scanning of the image identifies one or more known CVEs in the image or its included software packages.
Because the vulnerable image is provided as the chart's default image, users who deploy the chart without modifying the image configuration are exposed to the identified vulnerabilities.
**Expected Behavior**
The Helm chart should provide a reasonably current and security-maintained container image as its default image, without known high-impact or otherwise relevant vulnerabilities where a patched image is available.
We recognize that the image tag in a Helm chart may be intended as an initial/default value and that users may override it with another image or tag. However, not all users will inspect the chart configuration or independently replace the default image before deployment. Therefore, the chart's default configuration should provide a secure, supported image rather than relying on users to discover and remediate vulnerabilities themselves.
When a vulnerability is identified in the default image, maintainers should update the chart to reference a patched image version when one is available and document any required image override or upgrade procedure.
helm chart version: 2.17.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting charts/apisix/charts/etcd-12.0.18.tgz and the Helm chart configuration that selects docker.io/bitnamilegacy/etcd:latest. Check the image for known CVEs and determine whether a supported patched image is available. Done means the default chart image is updated or the required override and upgrade procedure are documented, with the chart still deployable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100