Poodle Attack - Security flaw in SSL v3 - ESET blocking

[rugk 397]

Nicknamed POODLE – it’s an acronym for Padding Oracle On Downgraded Legacy Encryption – Engadget reports that the bug “allows a man-in-the-middle attacker to decrypt HTTP cookies,” on SSL 3.0. Although SSL 3.0 is around 15 years old, it is still widely used in most web browsers and as a backup on servers if modern protocols fail to connect. Worryingly, “prospective attackers can force a server to default back to SSL 3.0 for the sake of the exploit.”

hxxp://www.welivesecurity.com/2014/10/15/poodle-attack-google-uncovers-major-flaw-ssl-3-0/

 

So this should be the end of SSL v3.

 

Now my suggestion for the ESET products...

What about making this?

[rugk 397]

Thanks @planet.

 

And what do you say about this @ESET?

[rugk 397]

What do you say about this suggestion, ESET?

[rugk 397]

Someone from the moderators or the ESET stuff:

Would you please so kind to answer me?

[rugk 397]

This suggestion is now more than one month old...

What do you think about this, ESET?

 

It was discovered that also some TSL implementations can be affected by this vulnerability, but still SSL v3 is the main point of attack.

So isn't it a good idea to block not only SSL v2, but also SSL v3 with the SSL scanning of ESS or ESET NOD32?

[Utini 1]

Very good suggestion !

[rugk 397]

Thanks, @Utini.

 

And what does ESET say about this?