New Java vulnerability, CVE-2013-0422, released 1/11/13

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

New Java vulnerability, CVE-2013-0422, released 1/11/13

Not applicable

Hello all,

Just wondering if anyone might be able to tell me whether this vulnerability, CVE-2013-0422, is being addressed? And, if so, when could we expect to see a patch for this? Thank you!

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0422&utm_source=dlvr.it&utm_medium=tw

http://msisac.cisecurity.org/advisories/2013/2013-006.cfm

1 accepted solution

Accepted Solutions

L5 Sessionator

Hi

Content release version 349 has been released today to cover this New Vulnerability .

Thank you

Numan

View solution in original post

4 REPLIES 4

L5 Sessionator

Hi

Content release version 349 has been released today to cover this New Vulnerability .

Thank you

Numan

Thank you for the prompt reply!

To get this content release 349 to successfully protect against these threats, what threat categories do we need to enable and apply policy (Virus / Spyware / Vulneability)? Because we just recently implemented the PA's and we dont' know the impact of turning all these categories to block right now. Thanks.

They are all by the category "critical". So if you at least set "critical" to default action: block (instead of default) you should be safe.

Generally speaking using this profile is recommended:

critical: block

high: block

medium: block

low: default

informational: default

Default means the default action that PA has set for this vuln.

For example:

critical 35273 Oracle Java Runtime Environment Remote Code Execution Vulnerability CVE-2013-0422  reset-client 3.1.0

means that if detected the default action is "reset-client" (which includes a logentry aswell).

While:

critical 35276 Adobe Reader JPEG File Parsing Memory Corruption Vulnerability CVE-2013-0603 APSB13-02 alert 3.1.0

means that the default action is to only produce a logentry.

But if you set the default action for critical to block then both above will block (drop) the session if detected.

Also the 349 update only updates vuln signatures (the IPS stuff).

  • 1 accepted solution
  • 2424 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!