Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Signatures
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Snort-sigs] new rule for detect SAP WAS syscmd access

from [Frank Knobbe] Network Security [Permanent Link]
Subject: Re: [Snort-sigs] new rule for detect SAP WAS syscmd access
Date: Thu, 10 Nov 2005 04:41:09 -0600 
On Thu, 2005-11-10 at 09:38 +0100, rmkml wrote:

web-attacks.rules:alert tcp $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS 
(msg:"WEB-ATTACKS SAP WAS syscmd access"; flow:to_server,established; 
uricontent:"/sap/bc/BSp/sap/menu/fameset.htm"; nocase; 
uricontent:"sap-syscmd"; nocase; classtype:web-application-activity;)

http://www.cybsec.com/vuln/CYBSEC_Security_Advisory_Multiple_XSS_in_SAP_WAS.pdf



While the paper also lists /fameset.htm, I'm curious if this not a typo
and is supposed to be /frameset.htm.

Did you test your rule before submission on an SAP install and does the
SAP application in fact use a mistyped page named fameset.htm, or did
you just write the rule based on the information in the PDF?

Regards,
Frank


-- 
It is said that the Internet is a public utility. As such, it is best
compared to a sewer. A big, fat pipe with a bunch of crap sloshing
against your ports.

Attachment: signature.asc
Description: This is a digitally signed message part

[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Snort-sigs] new rule for detect SAP WAS syscmd access, rmkml
Next by Date:  Re: [Snort-sigs] new rule for detect SAP WAS syscmd access, rmkml
Previous by Thread:  [Snort-sigs] new rule for detect SAP WAS syscmd access, rmkml
Next by Thread:  Re: [Snort-sigs] new rule for detect SAP WAS syscmd access, rmkml
Indexes:  [Date] [Thread] [Top] [All Lists]