Story

Exploiting bug in Supermicro hardware is as easy as connecting to port 49152.

Preview

Well, there's your problem (Score: 1)

by fishybell@pipedot.org on 2014-06-23 04:05 (#280)

Why would I run IPMI on a public network? If work needs done remotely, that's what VPNs, etc. are for. Not only that, they shouldn't even be accessible to any user (or even super user) on any computer (desktop, server, phone, etc.) that doesn't have direct access to the IPMI network. There's a damn good reason why IPMI usually runs on it's own nic. To me, it's the holy grail of hacking targets so of course it's either locked down tight by dividing it into it's own network with strictly guarded access or it's disabled. There should never be any in-between.

Re: Well, there's your problem (Score: 2, Insightful)

by fatphil@pipedot.org on 2014-06-24 07:04 (#28Q)

For the same reason that people run phpadmin (or whatever it's called) on a public network. The number of probes to my webserver tell me that a lot of people (or at least a lot of scripted clients) expect there to be administrative tools publicly accessible.

However, it should have been obvious that there would be problems - the fact that it's called the "Intelligent" Platform Management Interface implies that there'll be something totally braindead about it or its implementation.

Moderation

Time Reason Points Voter
2014-07-16 20:55 Insightful +1 kerrany@pipedot.org

Junk Status

Not marked as junk