Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always consider casting sanitization #292

Merged
merged 1 commit into from
Jan 2, 2015

Conversation

JDGrimes
Copy link
Contributor

There are two different sanitization checks in the VIP.ValidatedSanitizedInput sniff. Only one of
them was considering that casting is a form of input sanitization. I’ve
moved the casting check out of the conditional it was in, and now the
$is_casted value is being checked for all sanitization checking paths.

Includes unit tests.

Fixes #179

There are two different sanitization checks in this sniff. Only one of
them was considering that casting is a form of input sanitization. I’ve
moved the casting check out of the conditional it was in, and now the
`$is_casted` value is being checked for all sanitization checking paths.

Includes unit tests.

Fixes WordPress#179
westonruter added a commit that referenced this pull request Jan 2, 2015
Always consider casting sanitization
@westonruter westonruter merged commit f1423c4 into WordPress:develop Jan 2, 2015
@JDGrimes JDGrimes deleted the issue/179 branch January 18, 2015 19:59
@GaryJones GaryJones added this to the 0.4.0 milestone Aug 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Casting to an integer should be considered input sanitization
3 participants