Composer packages with hyphen not resolved to correct CPE
See original GitHub issueDescribe the bug
We currently have php-ampqlib
as a composer dependency in our project at version 2.6.3
. When running the dependency check, lots of vulnerabilities are erroneously listed against the package.
This is because the CPE assigned is cpe:2.3:a:php:php:2.6.3:*:*:*:*:*:*:*
which is for the main PHP library. Which means we end up with hundreds of vulns that aren’t even related.
Version of dependency-check used 6.0.3
Log file currently don’t have but can be provided
To Reproduce Steps to reproduce the behaviour:
- Require
php-ampqlib
as a dependency in a composer project - Run DependencyCheck on the project
Expected behaviour Only vulns related to the package should be shown - not those of PHP entirely
Additional context N/A
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Use installed file which name contain hyphen via composer
1 Answer 1 ... Since composer packages aren't case-sensitive, hyphens (or dash) are used as an alternative to CamelCace notation: Note that ...
Read more >Troubleshooting - Composer
Try clearing Composer's cache by running composer clear-cache . Ensure you're installing vendors straight from your composer.
Read more >Apple Music Style Guide
Featuring, Contributor Roles, Composer, Lyricist, Songwriter subsections now called Non-Primary Artist. Updated Section 5.1 Original Release Dates definition.
Read more >CPE Bach's “Sing ihm voll Rührung, o Zion” (Wq 212)
the problem in a long note regarding the first St. Matthew Passion of C.P.E. Bach: One can deduce that he was not entirely...
Read more >Tivoli Workload Scheduler: Scheduling with the agent for z/OS - IBM
If you have a problem with your IBM software, you want to resolve it quickly. IBM ... Note: Run this step only if...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jeremylong This is definitely a bug that package names are split up incorrectly on hyphens and then false positives are generated for all name parts. Since dependency check version 6, our suppression list is growing extremely.
@jeremylong Thank you for the explanation. Due to the accumulation of false positives since the last major update in combination with packages with hyphens in the name I assumed a bug. But if the behavior is so desired or necessary to avoid false negatives, I create FP reports.