Replies: 1 comment
-
|
hello @sekveaja You can read about OS packages and their files here: https://trivy.dev/latest/docs/scanner/vulnerability/#handling-software-installed-via-os-packages
I quickly checked your image. It looks like Trivy doesn’t detect urllib3 as a language (python) package. Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
When install an OS Vendor patched package in example SLES 15 SP6
python311-urllib3-2.0.7-150400.7.21.1.noarch.
it will install in two ecosystems, in Python and server OS.
In the OS ecosystem we will see,
rpm -qa | grep urllib
python311-urllib3-2.0.7-150400.7.21.1.noarch
In Python ecosystem
pip list | grep urllib
For this CVE-2025-50181, NVD and Github Security Advisory recommended urllib3 > 2.5.0
If we look at Python ecosystem 2.0.7 is below the recommended version of NVD and GHSA.
If we look at SUSE ecosystem package python311-urllib3-2.0.7-150400.7.21.1.noarch has the right patch version.
When running trivy, we have no CVE reported.
Q1: Is it because at the OS level, patched has been applied where urllib3 module in Python will not generate CVE?
Q2: When you install with a package manager and it will install into 2 ecosystems, do the patch from OS ecosystem will override progamming langage (Python)?
Thank you in advance for the clarification.
Desired Behavior
See description
Actual Behavior
Se description
Reproduction Steps
Target
None
Scanner
None
Output Format
None
Mode
None
Debug Output
Operating System
"SLES" VERSION="15-SP6"
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions