The more I look at AWS and the more I cannot understand how IBM missed the opportunity of using massive zSeries installs with Linux LPARs for cloud computing. All the I/O, security, etc. problems had already been solved. CloudHSM? Ha, z15-TO1 & friends, I/O? Ha… mainframe!
-
-
Replying to @cynicalsecurity
If you think mainframes fundamentally solve security problems, we need to have a word about exploit mitigations in z/OS (or lack thereof). mainframes are equally or less secure than commodity x86. It's just that there are probably 2 people in the world trying to exploit them.
2 replies 0 retweets 12 likes -
Replying to @marcan42
Did you count me in or not? I spent quite some time hacking LPARs to little success, less now as I lost access to my hacking target, probably my incompetence but they actually had thought of stuff far more than x86.
1 reply 0 retweets 0 likes -
Replying to @cynicalsecurity
I wrote a trivial buffer overflow CTF level on z/OS USS, exploitable by dumping shellcode on the stack and overwriting the return addr. The kind of thing that hasn't worked on x86 for two decades... I mean, LPARs work, but so does Intel virtualization...
2 replies 0 retweets 1 like -
Replying to @marcan42 @cynicalsecurity
I'm curious - when did you write this exploit?
1 reply 0 retweets 0 likes -
Replying to @a_giorgio @cynicalsecurity
This was probably 3 years ago? But running on a slightly outdated ADCD version of z/OS for testing. We had a real mainframe for the actual competition, but I don't think anyone managed to solve it in time.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @cynicalsecurity
So where did you inject the shellcode into? I'm curious as to what was running in USS that you managed to exploit.
1 reply 0 retweets 0 likes
I wrote my own trivially vulnerable app. My point here is it would've been a lot harder, or impossible, to exploit on other OSes because z/OS is two decades behind in basic security mitigations as far as I can tell.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.