Skip to content

Add security and mitigation options for Memcached image #664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zyue110026 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add security and mitigation options for Memcached image #664

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -946,3 +946,21 @@ Kubernetes: `^1.19.0-0`
| useConfigMap | bool | `false` | |
| useExternalConfig | bool | `false` | |

## Security & Container Image Considerations

### Default Memcached Image Status

The default configuration of this Helm chart references `memcached:1.6.45`. While this is currently the latest official upstream release of Memcached, security scanners may flag known Common Vulnerabilities and Exposures (CVEs) present in the underlying base image packages.


### Mitigation Options

If your organizational policies or security requirements prohibit running images with known vulnerabilities, consider the following options:

1. **Override Default Image in `values.yaml`**
You can specify your own hardened or patched Memcached image, such as Docker Hardened Images [Memcached](https://hub.docker.com/hardened-images/catalog/dhi/memcached), using custom values during deployment:
```yaml
memcached:
image:
repository: your-custom-registry/memcached
tag: your-secure-tag