MediumGHSA-c7xr-736p-29j3CVE-2010-3666

TYPO3 is vulnerable to Insecure randomness in uniqid function

Published 21 Apr 2022 · Updated 6 Feb 2024

Is your project on an affected typo3/cms-install?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<4.1.14
Fixed in
4.1.14
Update to the fixed version for your release line, for example:composer require typo3/cms-install:^4.1.14
Affected
>=4.2.0 <4.2.13
Fixed in
4.2.13
Update to the fixed version for your release line, for example:composer require typo3/cms-install:^4.2.13
Affected
>=4.3.0 <4.3.4
Fixed in
4.3.4
Update to the fixed version for your release line, for example:composer require typo3/cms-install:^4.3.4
Affected
>=4.4.0 <4.4.1
Fixed in
4.4.1
Update to the fixed version for your release line, for example:composer require typo3/cms-install:^4.4.1

Details

TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 contains insecure randomness in the uniqid function.

Is GHSA-c7xr-736p-29j3 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-install, and gives you the command that fixes it.

More advisories for typo3/cms-install

  • LowCVE-2024-55891TYPO3 Information Disclosure via Exception Handling/Logger · 14 Jan 2025
  • LowCVE-2023-47126Information Disclosure in typo3/cms-install tool · 14 Nov 2023
  • LowCVE-2010-5100TYPO3 Cross-Site Scripting vulnerability in the Install Tool · 17 May 2022
  • MediumCVE-2009-3636Typo3 API Install Tool vulnerable to Cross-site Scripting · 2 May 2022
  • MediumCVE-2010-3671TYPO3 is vulnerable to Session Fixation · 21 Apr 2022
typo3/cms-install security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.