Closed ohader closed 9 months ago
See:
This repo only tracks the advisories: check https://github.com/advisories for the latest updates.
typo3/cms-core
should not replace with a deathstar range there: self.version
or something more precise should be used to avoid affected version ranges.
For the records: A recent change at GitHub "hallucinated" a Composer package, which caused this behavior (side-note: the original advisory was from 2010, Composer was established in 2012 - two years later). → GitHub advisory change: https://github.com/github/advisory-database/commit/b403b051308beeee5bfe57a59103735a2170eb36
Description
The package
typo3/cms-saltedpasswords <0.2.13
suddenly is marked as insecure and blocks the installation thetypo3/cms-core
package (due to having areplaces
declaration fortypo3/cms-saltedpasswords: *
intypo3/cms-core
).Observation
A bunch of changes were committed recently to
roave/security-advisories
- where theconflict
declaration does not match with the actual original commit insensiolabs/security-advisories
, for instance:conflict
fortypo3/cms-saltedpasswords
, original commit is aboutmediawiki/semantic-media-wiki
(https://github.com/FriendsOfPHP/security-advisories/commit/baf9dd701ef517f3d16c41a90ef1966843e9913b)conflict
fortypo3/cms-frontend
,typo3/cms-backend
andtypo3/cms-install
, original commit is aboutmediawiki/semantic-media-wiki
(https://github.com/FriendsOfPHP/security-advisories/commit/baf9dd701ef517f3d16c41a90ef1966843e9913b)conflict
fortypo3/cms-frontend
, original commit is aboutmediawiki/semantic-media-wiki
(https://github.com/FriendsOfPHP/security-advisories/commit/baf9dd701ef517f3d16c41a90ef1966843e9913b)CLI commands used to reproduce the behavior