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.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Link | Tags |
---|---|
https://security-tracker.debian.org/tracker/CVE-2011-3583 | third party advisory |
https://access.redhat.com/security/cve/cve-2011-3583 | broken link |
https://typo3.org/security/advisory/typo3-core-sa-2011-002/ | vendor advisory |
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641682 | third party advisory |