CVE-2010-3670 json
TYPO3 is vulnerable to insecure randomness during hash generation in forgot password function
published 7y ago modified 4mo ago also GHSA-3276-p9f2-8q89 , EUVD-2022-1603
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
TYPO3 before 4.3.4 and 4.4.x before 4.4.1 contains insecure randomness during generation of a hash with the "forgot password" function.
Patch / fix
- packagist typo3/cms-frontend 4.3.4, 4.4.1
- typo3 typo3 4.3.4, 4.4.1
- github.com/TYPO3/typo3@09ab776 commit
- github.com/TYPO3/typo3@c03e944 commit
Is CVE-2010-3670 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-frontend | <4.3.4 >=4.4.0, <4.4.1 |
4.3.4 4.4.1 |
Classification
- Weakness
-
- CWE-326 Inadequate Encryption Strength
References
-
github.com
/TYPO3/typo3/commit/09ab77653161f23e266470a5984d4d5e64588355
web
-
github.com
/TYPO3/typo3/commit/c03e944d200bf427bb18cad15f2ad36bc83061c9
web
-
typo3.org
/security/advisory/typo3-sa-2010-012/#Insecure_Randomness
web, vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2010-3670
web, third-party-advisory
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=590719
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2010-3670
advisory
-
github.com
/TYPO3-CMS/frontend
package
Sources
- CVE List CVE-2010-3670
- GitHub Advisory GHSA-3276-p9f2-8q89
- NVD CVE-2010-3670
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.