Exploit Available for Cisco IOS Vulnerability
GNUman writes "Cisco's IOS vulnerability, posted by Slashdot and CERT, has now a published exploit available, as reported recently by CERT. While there are some some articles claiming that the Internet survived a major flaw, maybe with a publicly available exploit could script kiddies start creating havock?. jerw134 wanted to start a pool to find out when the exploit would be publicly available, here's the answer."
...the 'sploit is more easily available than the fix!
Anyone else gone through hell today trying to get the patch from Cisco?
Grrr... >-/
You're right on the money with the "maturity" comments, Jack. The way technology has been running, we have been in a constant state of trying to learn something new. We've never really had a chance to get "really good" at some of our technologies, before the next version or replacement technology arrived.
The Cisco situation is not due to bleeding edge issues though. They should have found this problem sooner.
It's also a shame we have to pat ourselves on the back a lot on slashdot. And as long as you're not bragging about $10k bonuses, make sure to not tell us how you didn't spend it on the EFF and FSF. ;-)
Beware he who would deny you access to information,
for in his heart he dreams himself your master.
What kind of graphics were these? They should have been already optimized to allow for quick loading.
Unless you're talking about high quality TIF's B&W vs. Color should not be making a difference in your load times.
-- taking over the world, we are.
I've already compiled this and tested against an internal router, fills up the input queue quite nicely. Requires libnet.h
-orbit0r
I had the impression that routing was a fairly straight-forward task and that 100% reliable software should be available for the routers. Has Cisco added frills to such an extent that the basic routing is compromised? Is this current problem associated with unnecessary features?
Here the exploit: http://www.securitylab.ru/_tools/shadowchode.tar.t ar .tar.gz file, incorrectly named.
It's
:wq
If you look at the release dates of some of the code that is not vulnerable to this attack, it goes back to early June. To me, it looks like this was identified almost two months ago. The question then is: Was this suddenly announced once a planned mile-marker in IOS revisions had been met....or once they suspected the exploit was in the wild?
Why does the author put "(void)" before every fprintf()? Can it be some kind of hidden signature?
They may use Juniper routers, but if your contract with them includes their maintenance of CPE they provided for you, and the CPE is Cisco, you're still screwed, aren't you?
Get off my launchpad!