Typo3 SQL injection due to faulty prepared statements
It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability. This issue can only be exploited if two or more parameters are bound to the query and at least two come from user input.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2011-3583US | critical9.8 | — | ||
It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability. T… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2011-3583WEB
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641682WEB
- https://github.com/TYPO3/typo3PACKAGE
- https://nvd.nist.gov/vuln/detail/CVE-2011-3583ADVISORY
- https://security-tracker.debian.org/tracker/CVE-2011-3583WEB
- https://typo3.org/security/advisory/typo3-core-sa-2011-002WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan