I have this file:
[ytti@lintukoto ~/tmp/ida]% file cat3k_caa-universalk9.SPA.03.03.00.SE.150-1.EZ.bin
It's image for Cisco Catalyst 3650 switch. The switch itself is running Cavium, probably Cavium Octeon CPU on Linux.
I think the file on top of it has some proprietary headers (possible hash of file integrity too). If I remove what I believe to be headers, I get this:
cat3k.mips: mc68010 demand paged executable not stripped
I can't get it open on IDA Pro, as it says it's binary file, and I need to choose entry point.
I'm pretty sure it's self-decompressing image, so I'd probably want to be able to decompress it as well. But at least unzip and gzip fail on me.
What I'm trying to accomplish is, the switch has certain command you use to escape proprietary process and access the Linux shell, before this command executes it presents you with a challenge and you have to give matching response, otherwise no soup^Wshell for you.
I was thinking of finding the string which complains about incorrect response, seeing which part of the code jumps there. I'd expect to find some comparison there, and then I'd just flip the comparison around. With desired results that in future incorrect response would succeed (and correct response fail).
I don't expect any particular efforts from Cisco to avoid customers from breaking their own kit willfully, this is more of easy for them to prove, that customer didn't break it accidentally by going to linux shell and killing some process.
If there is some sort of integrity test of the file, then I might be shit out of luck.
But I'd love some tips how to actually
- decompress this
- get it open in IDA Pro in meaningful way
I can share the file upon request (it's useless without the switch, and if you own switch, you are eligible to the image, so I don't consider it 'warez').
The challenge looks like this:
SWITCH#request system shell
Activity within this shell can jeopardize the functioning of the system.
Are you sure you want to continue? [y/n] y
Please enter the shell access response based on the above challenge (Press "Enter" when do>ne or to quit.):
Key verification failed