This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UPDATE - IPS Pattern Update fixed

Hi Everyone,

We have tested that the new IPS patterns on the Up2Date server are fixed and working.

If your system is affected there are two ways to get the updated and fixed patterns:

1) WebAdmin (the preferred way)

- login to WebAdmin via https://YOUR_ASG_IP:4444
- go to left menu item “Network Security”
- go to sub menu item “Intrusion Prevention”
- disable the IPS system (if not already done)
- go to the last tab “Advanced”
- click on the green “+” sign under “Modified rules”
- enter under “Rule ID”: 15851 and check “Disable this rule”
- click “Save”
- click again on the green “+” sign under “Modified rules”
- enter under “Rule ID”: 16576 and check “Disable this rule”
- click “Save”
-     go back to the first tab and activate the IPS system again

This will fix the problem and install the new IPS pattern.

PLEASE NOTE: Depending on the speed and workload of your ASG it can take a minute!

2. Command line (only for experienced users)
-     login via SSH or local on console
-     become "root"
-     enter "echo 1 > /proc/net/nf_condition/ips"

That's all and will do the following:

*     it will bypass completely the IPS system on lowest level (ASG is online then), independent if IPS is activated or deactivated on WebAdmin

*     the new IPS pattern will be fetched and installed

*     the next IPS pattern update we will provide later today will remove this bypass automatically and the ASG works like configured (with new pattern)

If your ASG uses ACC as an Up2Date cache: do the same above for these ASGs if there are affected. There is no todo on ACC.

If your ASG is not and was not affected, because IPS was turned off last 8 hours or not online and therefore didn't fetched the corrupt pattern then there is no action needed. The old, corrupt patterns are removed from the Up2Date server. It is safe the activate IPS now and set the ASG online again to fetch IPS pattern.

We are very sorry for this inconvenience.

Best regards,

Dominic Schmidl

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 15 years ago

Thanks Bruce for the clarification.

NLogan: Yes, you will need to have the IPS turned on to get the correct pattern updates. Astaro only updates patterns for features that are enabled. The pattern that fixes both the IPS and AV issues appears to be 12410.

MEINZJO: These are somewhat tricky questions. In regards to AV updates, every single AV vendor out there has, upon occasion, released bad definitions. I've seen it from every major vendor, such as Trend, McAfee, Sophos, and Symantec. McAfee had a particularly nasty one a couple of weeks ago. This is mostly due to the fact that definitions are written by humans and humans will always be fallible. In regards to both AV and Snort IPS rules and testing. It's a very fine line that's constantly moving. Most updates are created to protect against 0-day or even 0-hour exploits. If a vendor takes too long to do very comprehensive testing before release, many of their customers may have already gotten infected/compromized by the time that the definition set is released. I'm not particularly thrilled with the double whammy from this morning, but it can and will continue to happen. Just so long as it's a rare event.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Scott_Klassen over 15 years ago

Thanks Bruce for the clarification.

NLogan: Yes, you will need to have the IPS turned on to get the correct pattern updates. Astaro only updates patterns for features that are enabled. The pattern that fixes both the IPS and AV issues appears to be 12410.

MEINZJO: These are somewhat tricky questions. In regards to AV updates, every single AV vendor out there has, upon occasion, released bad definitions. I've seen it from every major vendor, such as Trend, McAfee, Sophos, and Symantec. McAfee had a particularly nasty one a couple of weeks ago. This is mostly due to the fact that definitions are written by humans and humans will always be fallible. In regards to both AV and Snort IPS rules and testing. It's a very fine line that's constantly moving. Most updates are created to protect against 0-day or even 0-hour exploits. If a vendor takes too long to do very comprehensive testing before release, many of their customers may have already gotten infected/compromized by the time that the definition set is released. I'm not particularly thrilled with the double whammy from this morning, but it can and will continue to happen. Just so long as it's a rare event.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data