ISSUES WITH CUSTOM VULNERABILITY

[noc_soc]

Hi All,

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.
Model: PA-4050
Software Version: 4.0.11

For this we register accesses can be made to the player JWPLAYER with parameters in the URL.
Examples:
http://www.xxxx.xx/media/players/jwplayer/player.swf?abouttext=xxxxxx&aboutlink=http://www.xxxx.xxx

http://www.xxxxx.xx/media/players/jwplayer/player.swf?file=http://xxxxx.xxx&image=http://xxxx.xxxx

http://www.xxxxx.xx/media/players/jwplayer/player.swf?file=http://xxxxxx.xxx&logo.file=http://xxxxx....xxxxxxx

To create it first was used in an attempt to record all requests containing .swf? and indicating the call with parameters:
OPERATOR: Pattern Match
CONTEXT: REQ-HTTP-HEADERS
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:
  OPERATOR: PATTERN-MATCH
  CONTEXT: HTTP-REQ-URI-PATH
  PATTERN: .*jwplayer /.*swf
And Condition 2
  OPERATOR: PATTERN-MATCH
  CONTEXT: HTTP-REQ-PARAMS
  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

[tettema · Accepted solution]

Hello,

I would suggest you look for /jwplayer/player.swf in the http-req-uri and a length of greater than 0 for the http-req-param-length.

[noc_soc]

It's just what we need.
Thanks for the reply