Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bugfix: SQL injection in custom field enum/set types
Reported by Peng Zhou @zpbrent
- Loading branch information
Showing
2 changed files
with
3 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16e7a94
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After implementation we have 3 comments and errors:
Existing enumset value is chosen for IP. Save. Result=Empty (does not save the value and leaves it as blank)
Previous enumset from 1.4.5 was ''value1','value2','value3''. Now it is converted to '''value1'',''value2'',''value3''' after upgrade.
If the enumset is modified/updated, it cannot be saved.
A) Required field = True, Version = 1.5.2
B) Change: added one more enum value. Click Save.
Error:
SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'custom_field1'. Failed to edit field