diff options
author | Derek Jones <derek.jones@ellislab.com> | 2011-04-19 23:13:48 +0200 |
---|---|---|
committer | Derek Jones <derek.jones@ellislab.com> | 2011-04-19 23:13:48 +0200 |
commit | 6ae70cc8499499b5d77d77ec8974f95873edb861 (patch) | |
tree | 85b39e2ae9018e77f6fe8647b1004f91764001ce /user_guide/changelog.html | |
parent | 9ce4385cfc976e309ee12c53726abfd4f066ac3f (diff) |
modified MySQL and MySQLi drivers to address a potential SQL injection attack vector when multi-byte character set connections are employed. (Does not impact Latin-1, UTF-8, etc. encodings)
Diffstat (limited to 'user_guide/changelog.html')
-rw-r--r-- | user_guide/changelog.html | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/user_guide/changelog.html b/user_guide/changelog.html index 945b10497..6eb80b38e 100644 --- a/user_guide/changelog.html +++ b/user_guide/changelog.html @@ -63,6 +63,10 @@ Change Log <p>Release Date: Not Released</p> <ul> + <li>Security + <ul> + <li>An improvement was made to the MySQL and MySQLi drivers to prevent exposing a potential vector for SQL injection on sites using multi-byte character sets in the database client connection. <p>An incompatibility in PHP versions < 5.2.3 and MySQL < 5.0.7 with <em>mysql_set_charset()</em> creates a situation where using multi-byte character sets on these environments may potentially expose a SQL injection attack vector. Latin-1, UTF-8, and other "low ASCII" character sets are unaffected on all environments.</p> <p class="critical">If you are running or considering running a multi-byte character set for your database connection, please pay close attention to the server environment you are deploying on to ensure you are not vulnerable.</p></li> + </ul> <li>General Changes <ul> <li>Added Session Class userdata to the output profiler. Additionally, added a show/hide toggle on HTTP Headers, Session Data and Config Variables.</li> |