Slashdot Mirror
Dangerous Java Flaw Threatens 'Virtually Everything'
Marc Nathoni writes with a ZDet article about a critically dangerous hole in the Java Runtime Environment. Due to the ubiquitousness of Java, this could prove a serious security problem. "Australia's Computer Emergency Response Team (AusCERT) analyst, Robert Lowe, warned that anyone using the Java Runtime Environment or Java Development Kit is at risk. 'Delivery of exploits in this manner is attractive to attackers because even though the browser may be fully patched, some people neglect to also patch programs invoked by browsers to render specific types of content,' said Lowe."
What about the people using it to run nuclear reactors?
The article sadly has little more information than the summary. It doesn't say which VMs, only that "exploit is browser independent, as long as it invokes a vulnerable Java Runtime Environment". In other words, the vulnerable VMs are vulnerable.
For an additional undetermined sum, Pure Hacking will offer an ambiguous and nefarious fix for the vulnerability.
>>Due to the ubiquitousness of Java, this could prove a serious security problem.
Ah! That would be 'ubiquity' then?
FFS editors!
That was yet another serious Java bug. Unless they've decided to review a story from January, which I guess is always possible.
Friday the 13th is the new April Fool's Day!
...at least we can be assured whatever disaster happens, it will happen slowly. Just kidding!
Just because you are paranoid doesn't mean there isn't an invisible demon out to eat your face.
Among other things, it has been confirmed that cellphones, computers, handhelds, iPods, small children, toasters, garage door openers and SUV owners are all vulnerable to this flaw.
The only device that isn't vulnerable to this is the Nintendo Wii. The theory is that the swinging of Wiimotes manages to sling the problematic code away from your device.
If you think that your computer might be at risk, pick it up and start spinning in big circles. This might create enough force to dislodge any vicious code.
Stop the Slashdot effect! Don't read the articles!
And then there is a buffer overflow event, causing data packed collisions, next thing you know I've got your mocha executing in my late.
whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
Oh, and Sun wouldn't have had this problem if they'd used pure Java code rather than relying on an existing library.
Yes. If only Sun would toss out all the C and re-implement their JVM in Java. How you'd launch the Java-based JVM is not clear, but once you got it going you'd never have to worry about buffer overflows again.
Well, if y'all goin' for the pure-Java solution, y'all obviously do the BIOS and bootleg^Wbootloader in Java, too.
I mean, C is just portable Assembler, right? If C is the source of all them evil buffer overflows, I reckon that means Assembler's got 'em, too?
Heck: me an' Jethro wuz wonderin' how these here computers ever got far enough along for the Sun to 'shine and the Java to perk.
Yep. I reckon only them city slickers with all their fancy talk do anything but Java anymore, buncha used car salesmen.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
That's probably because the bug inside had failed and the battery started corroding causing it to expand and crack the mug.
I just got done installing Java in 3 computer labs, and took the extra step of turning off that damn annoying autoupdate feature in the Java Control Panel on every machine. Crap, there goes my weekend...
I am not left-handed, either!
Am I the only one who originally read this as: Dangerous Lava Flow Threatens 'Virtually Everything'?
"Evil will always triumph over good, because good is dumb." - Dark Helmet (Spaceballs)
You know it is. Java is Write Once, Run Anywhere, remember?
This hole might have been a bit easier for Sun to patch if they hadn't made the automatic updater, jusched.exe such an unstable and annoying piece of junk. Or if they made updates work at all. My JRE is still beta 2 and has never seen an update since.
Screw it. I run Windows anyway, it's not like my system isn't already full of holes. What's one more?
Done with slashdot, done with nerds, getting a life.
Bunch of FUD-spreading fear-mongers. Hrumph.
Plus if anyone does write an exploit it will take so long to load and run the thing that everyone will be patched anyhow. Hell, machines capable of running a Java exploit must still be at least five years away. The last time I checked you need about 2G of ram to run "Hello World" (the source takes about 700MB), and you'd best have a big page file to back it up too.
But Java is getting faster and less bloated. They are learning to profile the language using the same methods that geologists use to track the drift of continental plates.
Why is it that an infinite number of monkeys at an infinite number of typewriters would reproduce all human knowledge instantly, but they would take about 12 times the age of the universe to generate the Java API? Oh yeah, I guess they would still have to load the thing.
At least the language is object-oriented. It would be inexcusable to any non-object-oriented language to become so huge and rancid. Can you imagine generating anything so horrible in C, Python, Perl, GW Basic, Fortran, etc without having the benefits of containers with 40 levels of abstraction? I guess you could write several million noop commands for every particle in the universe, but the compiler might be able to optimise that out.
Hey, maybe if they add another 40EB of rancid filth to the language then someone might be able to declare an unsigned integer. Or maybe not.
I'm kidding, of course. I love the language. It's just fucking great.
Shoosh! Good job I switched to Vista then :-)