Although the custom signature document indicates the "http-req-headers" context excludes the ablity to match on the method/path/version/host info, I have found that you can at least match on the method and version info using this context.
I haven't tried to match path/host info, however, as there are specific contexts available for those headers.
The attached vulnerability sig XML looks for v1.1 in a GET method, it would be easy enough to modify it to look for 1.0.
<vulnerability-threat version="7.1.0"> <entry name="41002"> <signature> <standard> <entry name="sig-http-ver"> <and-condition> <entry name="And Condition 1"> <or-condition> <entry name="Or Condition 1"> <operator> <pattern-match> <qualifier> <entry name="http-method"> <value>GET</value> </entry> </qualifier> <pattern>\x48 54 54 50 2f 31 2e 31\x</pattern> <context>http-req-headers</context> <negate>no</negate> </pattern-match> </operator> </entry> </or-condition> </entry> </and-condition> <order-free>no</order-free> <scope>protocol-data-unit</scope> <comment>looks for http version 1.1 in header</comment> </entry> </standard> </signature> <default-action> <alert/> </default-action> <threatname>http-header-get-v1-1</threatname> <severity>informational</severity> <direction>client2server</direction> <comment>http 1.1</comment> <affected-host> <client>yes</client> </affected-host> </entry> </vulnerability-threat>
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!