TYPO3CMS
CVE-2010-3717
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 · uneditedThe t3lib_div::validEmail function in TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 does not properly restrict input to filter_var FILTER_VALIDATE_EMAIL operations in PHP, which allows remote attackers to cause a denial of service (memory consumption and application crash) via a long e-mail address string, a related issue to CVE-2010-3710.
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 t3lib_div::validEmail function in TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 does not properly validate email input when using PHP's filter_var with FILTER_VALIDATE_EMAIL. A remote attacker can trigger excessive memory consumption and application crash by submitting an excessively long e-mail address string, causing denial of service.
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.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.2.5= 4.2.6= 4.2.7= 4.2.8= 4.2.9= 4.2.10= 4.2.11CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Identify TYPO3 installation versionCheck the VERSION file in the TYPO3 root directory, or query the system via TYPO3 backend (Admin Tools > About > Version), or inspect t3lib/version.php for the $version constantAffected if Version is 4.2.0 through 4.2.14, 4.3.0 through 4.3.6, or 4.4.0 through 4.4.3
-
Locate the vulnerable t3lib_div::validEmail functionSearch the t3lib/div.php file (or t3lib/class.t3lib_div.php in later 4.x branches) for the validEmail method definitionAffected if The validEmail method uses PHP filter_var with FILTER_VALIDATE_EMAIL and accepts unsanitized email input
-
Identify code paths that call validEmail with user inputSearch source code for calls to t3lib_div::validEmail or \TYPO3\CMS\Core\Utility\DivUtility::validEmail, particularly in form handlers, user registration, comment systems, or any plugin accepting email addressesAffected if User-supplied email strings are passed directly to validEmail without prior length validation
-
Test for long email input handlingSubmit an email address containing several thousand characters (for example, a string of 5000+ characters containing @ and periods) to any form field that uses validEmail validationAffected if Application experiences excessive memory consumption, timeout, or crash when processing the long email string
You are affected if running TYPO3 version 4.2.0-4.2.14, 4.3.0-4.3.6, or 4.4.0-4.4.3 AND your application uses the validEmail function to validate user-submitted email addresses without length constraints.
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 dataUpgrade to TYPO3 4.2.15, 4.3.7, 4.4.4 or later; alternatively, implement input length validation on email fields to constrain string length before passing to filter_var.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3717 — 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-3717 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