Tuesday, October 11, 2011

VRT Rule Update for 10/11/2011, MS Tuesday

Join us as we welcome the introduction of the newest rule release for today from the VRT. In this release we introduce 48 new rules and make modifications to 20 additional rules.

There were two changes made to the snort.conf in this release.  Since the last of the Shared Object rules have been moved out of the pop3 and sql categories, the following two files are removed from the snort.conf:

# include $SO_RULE_PATH/pop3.rules
# include $SO_RULE_PATH/sql.rules


In VRT's rule release:
Synopsis: The Sourcefire VRT is aware of vulnerabilities affecting products from Microsoft Corporation.

Microsoft Security Advisory MS11-075:
The Microsoft Windows operating system contains a programming error that may allow a remote attacker to execute code on an affected system.

Rules to detect attacks targeting this vulnerability are included in this release and are identified with GID 1, SIDs 20253 and 20254.

Microsoft Security Advisory MS11-076:
The Microsoft Windows Media Player contains a vulnerability that may allow a remote attacker to execute code on an affected system via the loading of a dynamic-link library from a remote location.

Rules to detect attacks targeting this vulnerability are included in this release and are identified with GID 1, SIDs 18496 and 18497.

Microsoft Security Advisory MS11-077:
The Microsoft Windows operating system contains a vulnerability that may allow a remote attacker to execute code on an affected system.

Rules to detect attacks targeting this vulnerability are included in this release and are identified with GID 1, SIDs 20261 and 20269.

Microsoft Security Advisory MS11-078:
Microsoft Silverlight contains a programming error that may allow a remote attacker to execute code on an affected system.

A rule to detect attacks targeting this vulnerability is included in this release and is identified with GID 1, SID 20255.

Microsoft Security Advisory MS11-079:
Microsoft Forefront contains programming errors that may allow a remote attacker to execute code on an affected system.

Rules to detect attacks targeting this vulnerability are included in this release and are identified with GID 1, SIDs 20256 through 20260 and 20272.

Microsoft Security Advisory MS11-080:
The Microsoft Windows operating system contains a programming error that may allow a remote attacker to execute code on an affected system.

A rule to detect attacks targeting this vulnerability is included in this release and is identified with GID 1, SID 20270.

Microsoft Security Advisory MS11-081:
Microsoft Internet Explorer contains multiple vulnerabilities that may allow a remote attacker to execute code on an affected system.

Rules to detect attacks targeting these vulnerabilities are included in this release and are identified with GID 1, SIDs 20262 through 20268 and 20273.

Microsoft Security Advisory MS11-082:
The Microsoft Host Integration Server contains a vulnerability that may allow a remote attacker to cause a Denial of Service (DoS) against a vulnerable host.

A rule to detect attacks targeting this vulnerability is included in this release and is identified with GID 1, SID 20271.

In order to subscribe now to the VRT's newest rule detection functionality, you can subscribe for as low as $29 US dollars a year for personal users, be sure and see our business pricing as well at http://www.snort.org/store. Make sure and stay up to date to catch the most emerging threats!

5 comments:

  1. Can we get a bit of standardization on the naming of signatures? In this update alone there are four different naming schemes for MS IE. If they all started with WEBCLIENT IE (or something! pick one!) it would be easier for sorting and categorization :)

    * 1:20273 <-> ENABLED <-> SPECIFIC-THREATS Microsoft Internet Explorer jscript9 parsing corruption attempt (specific-threats.rules)
    * 1:20270 <-> ENABLED <-> WEB-CLIENT Microsoft Windows afd.sys kernel-mode memory corruption attempt (web-client.rules)
    * 1:20268 <-> ENABLED <-> SPECIFIC-THREATS Internet Explorer Marquee stylesheet object removal (specific-threats.rules)
    * 1:20266 <-> ENABLED <-> WEB-MISC IE8 Javascript negative option index attack attempt (web-misc.rules)
    * 1:20265 <-> ENABLED <-> SPECIFIC-THREATS IE null attribute crash (specific-threats.rules)
    * 1:20262 <-> ENABLED <-> WEB-CLIENT Microsoft Internet Explorer onscroll DOS attempt (web-client.rules)
    * 1:20261 <-> ENABLED <-> WEB-CLIENT Microsoft Windows win32k.sys kernel mode null pointer dereference attempt (web-client.rules)
    * 1:20255 <-> ENABLED <-> SPECIFIC-THREATS Microsoft Silverlight inheritance restriction bypass (specific-threats.rules)
    * 1:20254 <-> ENABLED <-> WEB-CLIENT Microsoft products oleaut32.dll dll-load exploit attempt (web-client.rules)

    ReplyDelete
  2. Tony --

    They are named that way on purpose.

    WEB-CLIENT rules would cover a more general attempt to exploit the vulnerability mentioned.
    SPECIFIC-THREATS rules cover a SPECIFIC attempt. (Known attempt to exploit the vulnerability)

    ReplyDelete
  3. Yes but there are some issues - like

    SPECIFIC-THREATS Microsoft Internet Explorer (ex. 20273)
    And
    SPECIFIC-THREATS Internet Explorer (Ex. 20268)
    AND
    SPECIFIC-THREATS IE (ex 20265)

    This seems like it could be streamlined.

    Also same business going on with web-client and IE8 and spelled out and abbreviated.

    ReplyDelete
  4. Ah. I see what you are saying. I'll see what I can do here.

    ReplyDelete
  5. Thanks Joel, for the most part the naming convention is great, but I've seen some of this meandering in windows/office/ie product vulns :) A simple review will reveal what i'm talking about!

    ~Tony

    ReplyDelete