01-08-2007 01:08 AM - edited 03-10-2019 03:24 AM
Hi,
Has someone been able to make an IPS signature for the new PDF XSS?
I have tried something on the http service engine, but I'm having troubles specifying the # symbol as well as the multiple characters that may be anything.
01-08-2007 12:57 PM
We are currently looking into several new PDF vulnerabilities for inclusion in an official signature update. In the meantime, you should consider using the string-tcp engine ?from-service? on #webports for a custom signature. The easiest way to encode most characters is to use the hex ASCII (ex: \x20 for space) representation or enclose them in a character class ([ ]). If you can provide any additional information into which specific vulnerability/exploit your trying to address I may be able to be of more assistance.
01-08-2007 11:17 PM
I am referring to following vulnerability:
http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here
01-09-2007 06:18 AM
In this case I think I would write a return web signature so that we detect malicious incoming web pages (instead of ones that have been clicked).
I would consider something along the following lines:
String.tcp
From service
Port: #WEBPORTS
Summary Mode: Summarize
Summary Key: Axxx
Event Key: Axxx
[Hh][Rr][Ee][Ff][=][\x22\x60][Hh][Tt][Tt][Pp][:]\x2f\x2f[^\x0d\x0a\x3e\x7e-\xff]+[.][Pp][Dd][Ff][\x23][^\x0d\x0a\x3e\x7e-\xff]+[=][Jj][Aa][Vv][Aa][Ss][Cc][Rr][Ii][Pp][Tt]\x3a
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide