Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Security tool scanned the hashicorp/consul:1.10.0-beta2 docker image and found the following CVE: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-4074
Steps to reproduce this issue
Kubernetes version: AKS v1.18.14 consul version: 1.10.0-beta2 and 1.9.5
Fixable CVE-2016-4074 (CVSS 7.5) found in component 'jq' (version 1.6-r0) in container 'consul', resolved by version 1.6_rc1-r0
The text was updated successfully, but these errors were encountered:
This vulnerability appears to be fixed in the version of jq (1.6-r0) we're bundling with the Consul Docker image at https://github.com/hashicorp/docker-consul/blob/master/0.X/Dockerfile#L19, but looks like it's being improperly flagged by some scanning tools still (see stedolan/jq#1136 (comment)).
jq
Sorry, something went wrong.
No branches or pull requests
Overview of the Issue
Security tool scanned the hashicorp/consul:1.10.0-beta2 docker image and found the following CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-4074
Reproduction Steps
Steps to reproduce this issue
Environment
Kubernetes version: AKS v1.18.14
consul version: 1.10.0-beta2 and 1.9.5
Security scan result
Fixable CVE-2016-4074 (CVSS 7.5) found in component 'jq' (version 1.6-r0) in container 'consul', resolved by version 1.6_rc1-r0
The text was updated successfully, but these errors were encountered: