-
Notifications
You must be signed in to change notification settings - Fork 732
New rule 941360 to detect JSFuck and Hieroglyphy at PL1 #1261
Conversation
|
Reminder: capture might be missing. |
|
You're right @fgsch. Thanks for pointing this out. I'll update the PR. |
spartantri
left a comment
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.
The space in the regex doesn't change the detection rate "@rx ![!+]\[\]"
|
jsfuck payloads are huge and not really understandable, I'm ok to have the E part in the auditlog but I'm curious about why adding %{MATCHED_VAR}? |
|
The comments carry the following remark: Did you notice that? |
spartantri
left a comment
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.
:)
my bad sorry :) it may be interesting to have this tested in front of a WP or some other CMS that uses lots of [] on their payloads before releasing 3.2 |
|
@dune73 you might want to rebase your branch using the latest commit in v3.2/dev so the tests pass. |
|
@fgsch: That's what I planned to do, but did not have time earlier. Now I did and it messed it up. So I'm planning to throw this away and do a new, clean PR. Here is what I did. What's wrong with this? I see the tests passing now. But anyways, I guess I should have cherrypicked the right commit. |
|
@dune73 not sure. I normally do the following (assuming origin points to this repo):
You should be able to fix this PR without closing it, for example:
|
682bc3e to
e8b254e
Compare
|
That worked nicely. Thank you @fgs. Merging now. At last. :-) |
This includes a new rule among the XSS rules and a couple of tests to go with it.