-
Notifications
You must be signed in to change notification settings - Fork 416
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
False positive while checking default wordpress config #77
Comments
Nope, vulnerable ;-) server {
listen 80;
server_name _;
rewrite /wp-admin$ $scheme://$host$uri/ permanent;
}
Test:
|
Yup, that is why I closed it. Just notified wp team |
This line is still on the support page. What should be the correct syntax? |
In order to fix this make sure to update from: rewrite /wp-admin$ $scheme://$host$uri/ permanent; Into: rewrite /wp-admin$ $scheme://$host$request_uri/ permanent; So the only change is if (!-e $request_filename) {
rewrite /wp-admin$ $scheme://$host$request_uri/ permanent;
rewrite ^(/[^/]+)?(/wp-.*) $2 last;
rewrite ^(/[^/]+)?(/.*\.php) $2 last;
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is default nginx config for WP: https://codex.wordpress.org/Nginx
And here is a line:
rewrite /wp-admin$ $scheme://$host$uri/ permanent;
Gixy warns us with next issue:
>> Problem: [http_splitting] Possible HTTP-Splitting vulnerability. Description: Using variables that can contain "\n" or "\r" may lead to http injection. ... Reason: At least variable "$uri" can contain "\n"
But this is false positive as Rewrite directive isn't vulnerable to CRLF.
The text was updated successfully, but these errors were encountered: