We are making the creation of a "Custom Signature" to detect an XSS vulnerability identified in the player JWPLAYER
The vulnerability occurs in / media / players / jwplayer / player.swf and HDSMediaProvider.swf.
Software Version: 4.0.11
For this we register accesses can be made to the player JWPLAYER with parameters in the URL.
To create it first was used in an attempt to record all requests containing .swf? and indicating the call with parameters:
OPERATOR: Pattern Match
PATTERN: .*jwplayer /. *swf \? (.*) Also with ".*jwplayer /. *swf \?"
This rule did not detect the parameters
Then we used 2 conditions with the following configuration:
And Condition 1:
PATTERN: .*jwplayer /.*swf
And Condition 2
PATTERN: .*((file)|(abouttext)|(image)) While it should detect any url parameter, these are the ones who were using for testing.
But it happened that not all parameters are detected. Therefore, the pattern will change to ((.+)|(abouttext)), since the minimum length is 7, but still does not detect any parameter.
The purpose of the rule is to detect any url with parameters
Sorry for the google translation
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!