-
Notifications
You must be signed in to change notification settings - Fork 175
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
Double escaping attribute values #143
Comments
Looks like I introduced a bug when attempting to fix HREF santization: f0057e2 However when I remove the double-sanitizing in that and test the output of the tests I wrote for that code... it doesn't pose a risk. That is, removing the double escaping still results in sanitized and safe to use output. As such, I'm going to remove the part of that prior commit that led to the double escaping. |
@buro9 will you be releasing a new version of bluemonday or should we (gitea) just pull a head? Ah I see you've already released 1.0.19 - Thanks! |
The current version of bluemonday is double escaping attributes. This PR updates bluemonday to the version that fixes this. (See: microcosm-cc/bluemonday#143 ) Signed-off-by: Andrew Thornton <art27@cantab.net>
The current version of bluemonday is double escaping attributes. This PR updates bluemonday to the version that fixes this. (See: microcosm-cc/bluemonday#143 ) Fix #19860 Signed-off-by: Andrew Thornton art27@cantab.net
Backport go-gitea#20199 The current version of bluemonday is double escaping attributes. This PR updates bluemonday to the version that fixes this. (See: microcosm-cc/bluemonday#143 ) Fix go-gitea#19860 Signed-off-by: Andrew Thornton art27@cantab.net
The current version of bluemonday is double escaping attributes. This PR updates bluemonday to the version that fixes this. (See: microcosm-cc/bluemonday#143 ) Fix go-gitea#19860 Signed-off-by: Andrew Thornton art27@cantab.net
The values of attributes are getting double escaped. As far as I can tell, the problem was introduced in f0057e2. In particular, the double-quote character and non-breaking spaces won't ever make it through sanitizing.
In code, I expect the following test to pass.
However, I get this output.
The text was updated successfully, but these errors were encountered: