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
Note: Problem could come from Syft output pycryptodome version 3.9.0, there is no such package in the container.
There is only python3-pycrytodome package in the container.
Environment:
$ grype --version
grype 0.79.4
In container image eco-system:
bash-4.4$ cat /etc/release
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
The text was updated successfully, but these errors were encountered:
What happened:
Scan on image that has python3-pycryptodome-3.9.0-150200.9.1.x86_64 installed.
It generates high vulnerability:
NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY
pycryptodome 3.9.0 3.19.1 python GHSA-j225-cvw7-qrx7 Medium
What you expected to happen:
According to SUSE Advisory CVE-2023-52323
Patch for this CVE is applied from version python3-pycryptodome-3.9.0-150200.9.1.x86_64
See with this link: https://www.suse.com/security/cve/CVE-2023-52323.html
SUSE Linux Enterprise Module for Basesystem 15 SP5
python3-pycryptodome >= 3.9.0-150200.9.1
Patchnames:
SUSE-SLE-Module-Basesystem-15-SP5-2024-601
Installed version in the container: python3-pycryptodome-3.9.0-150200.9.1.x86_64
rpm -qf /usr/lib64/python3.6/site-packages/pycryptodome-3.9.0-py3.6.egg-info/PKG-INFO
python3-pycryptodome-3.9.0-150200.9.1.x86_64
Conclusion: Installed version meet the minimal requirement patch from SLES 15.5 but Grype generate a vulnerability.
How to reproduce it (as minimally and precisely as possible):
FROM registry.suse.com/suse/sle15:15.5
RUN zypper in -y --no-recommends python3-pycryptodome=3.9.0-150200.9.1
ENTRYPOINT [""]
CMD ["bash"]
$ docker build -t "suse15.5_python3-pycryptodome:v1" .
$ grype --distro sles:15.5 suse15.5_python3-pycryptodome:v1
NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY
pycryptodome 3.9.0 3.19.1 python GHSA-j225-cvw7-qrx7 Medium
pycryptodome 3.9.0 python
python3-pycryptodome 3.9.0-150200.9.1 rpm
Note: Problem could come from Syft output pycryptodome version 3.9.0, there is no such package in the container.
There is only python3-pycrytodome package in the container.
Environment:
$ grype --version
grype 0.79.4
In container image eco-system:
bash-4.4$ cat /etc/release
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
The text was updated successfully, but these errors were encountered: