Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Java Zero-Day Malware Attack: 6 Facts
Newest First  |  Oldest First  |  Threaded View
moarsauce123
50%
50%
moarsauce123,
User Rank: Ninja
9/3/2012 | 4:03:44 PM
re: Java Zero-Day Malware Attack: 6 Facts
You are welcome, but then why do you still include links to this story in the many specialized and best of emails that come out days later? I received another link to this story today and by now I wondered if there is another flaw in the current version. Well, there is, but this article addresses the old, already fixed flaws. Your competition is much more on the ball.
1954 Stratocaster
50%
50%
1954 Stratocaster,
User Rank: Apprentice
8/31/2012 | 4:13:26 PM
re: Java Zero-Day Malware Attack: 6 Facts
I would like to see a "7th fact" about why Java 7 was vulnerable and Java 6 was/is not. Our current corporate standard -- yes, we have some corporate Web apps, both internal and contracted, which require Java -- is v6.x.
Mathew
50%
50%
Mathew,
User Rank: Apprentice
8/31/2012 | 10:53:35 AM
re: Java Zero-Day Malware Attack: 6 Facts
Thanks for the comment, moarsauce. Welcome to the fast-paced world of publishing, eh? Yes, after this story came out, Oracle issued its alert about the patch--which is a welcome fix. Our sister publication DarkReading has more on the Java 7 patch.
moarsauce123
50%
50%
moarsauce123,
User Rank: Ninja
8/30/2012 | 11:31:01 PM
re: Java Zero-Day Malware Attack: 6 Facts
There is already a update out that addresses the vulnerability. Maybe it is worthwhile to be more up to speed with content and publishing.
Leo Regulus
50%
50%
Leo Regulus,
User Rank: Apprentice
8/30/2012 | 8:08:13 PM
re: Java Zero-Day Malware Attack: 6 Facts
Please forgive me for writing when you weren't reading. I have brought this up several times in the past.
GET THIS TO YOUR EDITOR:
You have made some client-unfriendly changes to your format.
When we hit the 'Print' Icon, we expect to see the entire article as one page and relatively 'free' of (insert your own euphemism).
On this article, it was necessary to go to page 2 to get the whole article.
The result was also littered with (insert your own euphemism).
What should have printed on 2 sheets took at least 5.
What callous disregard for the environment and your clients resources!


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.