You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker scout treats [email protected] as vulnerable and reports that 4.0 has fixed the issue. But the CVE fix has been backported to 3.6.10 which is described in the CVE report in docker scout itself:
JGroups before 4.0 does not require the proper headers for the ENCRYPT and AUTH protocols from nodes joining the cluster, which allows remote attackers to bypass security restrictions and send and receive messages within the cluster via unspecified vectors. Fixes for this issue have been backported to versions 3.6.10.Final and 3.2.16.Final.
Reproduce
Add jgroups 3.6.20 to the image and analyze it with docker scout.
Expected behavior
jgroups 3.6.20 should not be reported as vulnerable
docker version
not important
docker info
not important
Additional Info
No response
The text was updated successfully, but these errors were encountered:
Thanks for reporting; looks like this is related to Scout, which is currently closed source, and not maintained in this repository. Issues related to scout are best reported in https://github.com/docker/scout-cli.
Description
Docker scout treats [email protected] as vulnerable and reports that 4.0 has fixed the issue. But the CVE fix has been backported to 3.6.10 which is described in the CVE report in docker scout itself:
https://scout.docker.com/vulnerabilities/id/CVE-2016-2141/org/axonivy
Reproduce
Add jgroups 3.6.20 to the image and analyze it with docker scout.
Expected behavior
jgroups 3.6.20 should not be reported as vulnerable
docker version
docker info
Additional Info
No response
The text was updated successfully, but these errors were encountered: