TYPO3CMS
CVE-2010-3666
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTYPO3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe TYPO3 application uses PHP's uniqid() function for generating tokens or session identifiers, but this function relies only on system time (microseconds) as entropy, making the output predictable and susceptible to brute-force guessing. An attacker who can observe or guess the timeframe of ID generation could predict future IDs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TYPO3CMS
< 4.1.14>= 4.2.0, < 4.2.13>= 4.3.0, < 4.3.4>= 4.4.0, < 4.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed TYPO3 versionLocate the Version file in the TYPO3 installation directory (typically at typo3/sysext/core/Classes/Version.php or check the release manifest). Open it and read the version number defined in the getVersion() method or similar.Affected if The version number is less than 4.1.14, OR between 4.2.0 and 4.2.12 inclusive, OR between 4.3.0 and 4.3.3 inclusive, OR between 4.4.0 and 4.4.0 inclusive.
-
Search for uniqid usage in session handling codeSearch the TYPO3 source code for calls to PHP's uniqid() function, particularly in files related to session management, token generation, or authentication (look in typo3/sysext/core/ and typo3/sysext/auth/). Use grep or similar to find 'uniqid(' patterns.Affected if The uniqid() function is found in session or token generation code, and the version falls within the affected ranges above.
-
Inspect session identifier generationExamine the file that generates session IDs (commonly in typo3/sysext/core/Classes/Session or similar session handling classes). Check if the session ID is generated using uniqid() or a similar time-based function.Affected if Session IDs are generated using uniqid() without additional entropy or cryptographic randomization.
You are affected if your installed TYPO3 version is within the ranges listed and the codebase contains uniqid() calls for session or token generation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.1.144.2.134.3.4
Upgrade TYPO3 to version 4.1.14, 4.2.13, 4.3.4, 4.4.1 or later, which replace uniqid() with cryptographically secure random token generation.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3666 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data