Closed (fixed)
Project:
Security Review
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2010 at 00:55 UTC
Updated:
9 Nov 2010 at 20:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
coltraneWhat have you set your untrusted roles to at Administer › Reports › Security review? If you don't have anonymous users marked as untrusted then the check will pass.
Comment #2
gregglesComment #3
matason commentedApologies for the initial bug report, here's a more detailed report:
Fresh install of Drupal 6.19
Logged in as user/1
Change the default input format to Full HTML
Download and install Security Review 6.x-1.0
Ensure anonymous user is marked as untrusted - (both anonymous and authenticated are checked by default)
Run checklist - everything passes
Expected - it possibly should flag up the potential dangers of the current input format configuration
It could be argued that without any additional permissions set this site is still secure(?), so...
Give anonymous users permission to view and add comments
Run checklist - everything passes
Expected - it should flag up the security vulnerability anonymous users can now exploit
I am happy to work on a patch if you feel that this behaviour is desirable.
Comment #4
coltraneThanks for the detailed report matason, I'll need to test from a fresh install cause I have yet to duplicate this bug on my Drupal 6 dev install. Security Review is *not suppose* to allow that to pass, it's checking for what you described (anonymous untrusted and Full HTML to default) so it's odd that it's failing.
Comment #5
coltrane(Setting back to active since there's no patch yet)
You're welcome to take a look at the code and see if you can spot any problem in this check.
Comment #6
gregglesI think I've figured this out.
Security Review is looking for the roles that can use the input format. If you complete the steps exactly as matason described that will be the case. However, as soon as you click "configure" in the full html input format and then click save on the configuration screen (without changing anything) then security report will recognize it as a problem.
So, I now check to see if the filter is the default filter and if it is then say all roles can use it.
Comment #7
matason commentedThanks @greggles, you beat me to it, the patch works.
I repeated the steps in #3 with it applied, the report now indicates that "Untrusted users are allowed to input dangerous HTML tags"
Good work!
Comment #8
coltraneNice, thanks greggles and matason. What a confusing bug. The workflow bug should be fixed in core.
I committed #6 with a modification to the help message. http://drupal.org/cvs?commit=441960