Skip to content

fix: Avoid FPs for Symfony Polyfill as framework#7543

Merged
jeremylong merged 1 commit intodependency-check:mainfrom
sigv:fp/7542
Mar 22, 2025
Merged

fix: Avoid FPs for Symfony Polyfill as framework#7543
jeremylong merged 1 commit intodependency-check:mainfrom
sigv:fp/7542

Conversation

@sigv
Copy link
Copy Markdown
Contributor

@sigv sigv commented Mar 21, 2025

Description of Change

Since package name matching change, Symfony Polyfill is being matched lossy as Symfony framework. However, it is an independent project, with an independent versioning scheme.

This can be observed in CVE-2022-23601 match. The advisory was patched in Symphony framework versions 5.3.15, 5.4.4 and 6.0.4. (Latest framework version is 7.2.4.) Meanwhile, Polyfill project has latest version as 1.31.0. This understandably is considered a vulnerable version number.

Related issues

Have test cases been added to cover the new functionality?

no

Since package name matching change, Symfony Polyfill is being matched lossy as Symphony framework. However, it is an independent project, with an independent versioning scheme.
@boring-cyborg boring-cyborg Bot added the core changes to core label Mar 21, 2025
@jeremylong jeremylong merged commit 27dcba2 into dependency-check:main Mar 22, 2025
5 checks passed
@sigv sigv deleted the fp/7542 branch March 24, 2025 10:01
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

core changes to core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FP]: Symfony Polyfill is matched as Symfony framework

2 participants