First published: Sun Jan 27 2013(Updated: )
classes/GoogleSpell.php in the PHP Spellchecker (aka Google Spellchecker) addon before 2.0.6.1 for TinyMCE, as used in Moodle 2.1.x before 2.1.10, 2.2.x before 2.2.7, 2.3.x before 2.3.4, and 2.4.x before 2.4.1 and other products, does not properly handle control characters, which allows remote attackers to trigger arbitrary outbound HTTP requests via a crafted string.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/moodle/moodle | =2.4.0 | 2.4.1 |
composer/moodle/moodle | >=2.3.0<2.3.4 | 2.3.4 |
composer/moodle/moodle | >=2.2.0<2.2.7 | 2.2.7 |
composer/moodle/moodle | >=2.1.0<2.1.10 | 2.1.10 |
TinyMCE Spellchecker | =2.0 | |
TinyMCE Spellchecker | =2.0-a1 | |
TinyMCE Spellchecker | =2.0-a2 | |
TinyMCE Spellchecker | =2.0-b1 | |
TinyMCE Spellchecker | =2.0-b2 | |
TinyMCE Spellchecker | =2.0-b3 | |
TinyMCE Spellchecker | =2.0-rc1 | |
TinyMCE Spellchecker | =2.0.1 | |
TinyMCE Spellchecker | =2.0.2 | |
TinyMCE Spellchecker | =2.0.3 | |
TinyMCE Spellchecker | =2.0.6 | |
Moodle | =2.1.0 | |
Moodle | =2.1.1 | |
Moodle | =2.1.2 | |
Moodle | =2.1.3 | |
Moodle | =2.1.4 | |
Moodle | =2.1.5 | |
Moodle | =2.1.6 | |
Moodle | =2.1.7 | |
Moodle | =2.1.8 | |
Moodle | =2.1.9 | |
Moodle | =2.2.0 | |
Moodle | =2.2.1 | |
Moodle | =2.2.2 | |
Moodle | =2.2.3 | |
Moodle | =2.2.4 | |
Moodle | =2.2.5 | |
Moodle | =2.2.6 | |
Moodle | =2.3.0 | |
Moodle | =2.3.1 | |
Moodle | =2.3.2 | |
Moodle | =2.3.3 | |
Moodle | =2.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-6112 is considered a medium severity vulnerability due to its potential to allow remote attackers to exploit it.
To fix CVE-2012-6112, upgrade to Moodle version 2.4.1, 2.3.4, 2.2.7, or 2.1.10 or later.
CVE-2012-6112 affects TinyMCE Spellchecker versions up to 2.0.6 and Moodle versions prior to 2.1.10, 2.2.7, 2.3.4, and 2.4.1.
CVE-2012-6112 exploits the improper handling of control characters which can lead to information disclosure or remote code execution.
There is no official workaround for CVE-2012-6112, so upgrading to the fixed versions is the recommended action.