-
Notifications
You must be signed in to change notification settings - Fork 577
Open
Labels
bugSomething isn't workingSomething isn't workinghigher priorityIssues we'd like fixed sooner rather than later, often ones that come directly from users.Issues we'd like fixed sooner rather than later, often ones that come directly from users.
Milestone
Description
Description
When running cve-bin-tool on windows and producing an sbom, jar files seem not to be identified at all.
To reproduce
Steps to reproduce the behaviour:
- Create new directory
- Download a jar file, for examples this one: https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.24.3/log4j-core-2.24.3.jar
- Run a scan and produce an sbom, for example:
cve-bin-tool . --sbom-format json --sbom-type cyclonedx --sbom-output sbom-output.json
Expected behaviour:
Running the same scan on linux, the jar file is identified as:
{
"type": "library",
"bom-ref": "2-log4j",
"name": "log4j",
"version": "2.24.3",
"supplier": {
"name": "apache"
},
"cpe": "cpe:/a:apache:log4j:2.24.3",
"evidence": {
"occurrences": [
{
"location": "/tmp/cve-bin-tool-lc9c7g5g/log4j-core-2.24.3.jar.extracted/META-INF/maven/org.apache.logging.log4j/log4j-core/pom.xml"
}
]
}
}
Version/platform info
Version of CVE-bin-tool: 3.4
Installed from pypi or github? pypi
Operating system:
OS Name: Microsoft Windows Server 2022 Datacenter
OS Version: 10.0.20348 N/A Build 20348
Python version: 3.12.10
Anything else?
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinghigher priorityIssues we'd like fixed sooner rather than later, often ones that come directly from users.Issues we'd like fixed sooner rather than later, often ones that come directly from users.