DependencyTrack / DependencyTrack/dependency-track
False positives with Zope and Plone
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
I am receiving several reports of vulnerabilities in Plone that reference versions of Plone not included in my SBOM.
PYSEC-2006-9
PYSEC-2006-10
PYSEC-2008-15
PYSEC-2009-17
This one is compounded by referencing a completely different package https://pypi.org/project/Products.PlonePAS/ which is a dependency of Plone. The version of Products.PlonePAS in my SBOM is 8.0.5
PYSEC-2011-32
PYSEC-2017-148
Zope and Zope2 are major dependencies of Plone often used together so I am including those false positives here too.
PYSEC-2010-33
### Steps to Reproduce
1. Create python venv and install plone `uv pip install plone -c https://dist.plone.org/release/6.1.3/constraints.txt`
2. Install cyclonedx-py `uv pip install cyclonedx-py`
3. Generate SBOM `cyclonedx-py environment --output-format=json -o="sbom.json"`
4. Upload SBOM to Dependency-Track
### Expected Behavior
No report for the component version.
### Dependency-Track Version
4.14.1
### Dependency-Track Distribution
Container Image
### Database Server
N/A
### Database Server Version
_No response_
### Browser
N/A
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported
Contributor guide
Assessment
This issue has not been assessed yet.