5 ms·
Ok, that finally makes a bit of sense about "if" this is true, how it might be carried out. And I agree with the author that the simplest action for a chip on t
by ChuckMcM 8y ago
Ok, that finally makes a bit of sense about "if" this is true, how it might be carried out. And I agree with the author that the simplest action for a chip on the SPI bus would be to hold the MISO line low during power on to suggest to the BMC chip that its QSPI flash isn't programmed (note that QSPI starts up as 'regular' SPI and then switches over[1]). I would guess that the next thing the BMC would do is assume its on the factory floor and hasn't had firmware loaded yet and so it would attempt to boot via TFTP from some server to start the firmware loading process.
FWIW at NetApp the firmware engineers called the BMC the 'BiteMeChip' because they always caused issues when bringing up a new filer motherboard. They were finicky, were often hard to update, and when misbehaving could completely screw up the system.
So I can see this as a vulnerability but really I'd want to stick some probes on that 'mystery' chip and make sure it wasn't just some LC filter or something which is shunting off noise on the data lines.
[1] https://github.com/ChuckM/stm32f469i/tree/master/demos/qspi https://github.com/ChuckM/stm32f469i/tree/master/demos/qspi
- SlowRobotAhead 8y agoAgreed on finally makes sense. Depending on what article it made it sound like a chip that sat between CPU and RAM or some external cache that was intercepting some pattern of data and real time buffering then modifying the output - which at CPU/RAM speeds made no sense. A chip holding and SPI line down - makes way more sense.
- ispiansclsda 8y ago> the simplest action for a chip on the SPI bus would be to hold the MISO line low during power on MISO is master-in, slave-out for anyone not familiar with serial peripheral interface jargon. Usually, the slave quad-SPI memory would send the configuration over this line, so pulling it low should dump the real data to ground.
- fkd221 8y agoBruce Schneier talked in 2013 already on BMC security linking to a paper [0] from Dan Farmer who did an Internet scan to find that ~230,000 BMCs were exposed to the Internet of which 90% could be compromised [1], yikes. [0] https://www.schneier.com/blog/archives/2013/01/the_eavesdroppi.html [1] http://fish2.com/ipmi/river.pdf
- amelius 8y agoOne question: how do you hold an existing line low without drawing lots of current, and without cutting that line first?
- akiselev 8y ago"Lots of current" in this case would only be about 20mA, generating heat that you can easily dissipate from just the surface of a 0201 resistor. I doubt many microprocessors have pins that can drive higher current than that. Realistically, in order to drive it low you don't have to bring it down to 0V. Most 5V chips will stop registering logic high around 2.5-3.3V for example.
- dbcurtis 8y agoThese days 20mA is a "high current" I/O. When you do the math on an 88-pin package, 20mA * N active outputs gets big pretty fast. The max total I/O current can be found somewhere around page 987 of the data sheet... don't stop reading early... :) (edit: 88 I/O is a modest size microcontroller sort of chip)
- Dylan16807 8y agoI don't understand how this is relevant to holding a single pin low.
- 8note 8y agoit's even easier than the comment above suggests
- dbcurtis 8y agoIt's not like the MISO line is tied to a power rail. You just need to sink more current than the output of the chip you are trying to override. So the driver is likely in the single digit milliamp range, and in any case, you don't care if you toast the output driver on that chip. In fact, if you do, bonus!