qschulz has quit [Remote host closed the connection]
zibolo_ has quit [Ping timeout: 245 seconds]
qschulz has joined #u-boot
zibolo has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
haritz has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
clamor has joined #u-boot
persmule has quit [Remote host closed the connection]
_whitelogger has joined #u-boot
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
gsz has joined #u-boot
gsz has quit [Ping timeout: 244 seconds]
ungeskriptet has joined #u-boot
Jones42 has joined #u-boot
ikarso has joined #u-boot
Poltawer has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
gsz has joined #u-boot
gsz has quit [Ping timeout: 260 seconds]
Poltawer has quit [Ping timeout: 240 seconds]
Poltawer has joined #u-boot
gsz has joined #u-boot
clamor has quit [Ping timeout: 245 seconds]
clamor has joined #u-boot
gsz has quit [Ping timeout: 240 seconds]
goliath has joined #u-boot
bjoto has quit [Remote host closed the connection]
haritz has joined #u-boot
haritz has quit [Changing host]
haritz has joined #u-boot
mmu_man has joined #u-boot
persmule has joined #u-boot
gsz has joined #u-boot
dsimic has quit [Ping timeout: 240 seconds]
dsimic has joined #u-boot
gsz has quit [Ping timeout: 252 seconds]
vagrantc has joined #u-boot
warpme has joined #u-boot
<vagrantc>
hey folks ... does this CVE against u-boot have any real merit? https://www.cve.org/CVERecord?id=CVE-2025-45512 ... it is firstly against an ancient version, and all the "exploits" require access to the u-boot console ... i mean, locking down the u-boot console might be a good thing to be able to do... but is it really an exploit?
<vagrantc>
am i missing something?
<vagrantc>
at a quick glance, it does not look like it actually bypasses any security measures ... just uses measures that have no lockdown mechanisms
<vagrantc>
(for extra fun, it mentions some raspberry pi specific commands, even though the version it is talking about is from 7 years before the raspberry pi even existed)
<vagrantc>
let alone had support in u-boot
<vagrantc>
good ol' u-boot v1.1.3
<vagrantc>
so i guess, in short, is there anything to actually be done about this one?
pitillo has quit [Quit: leaving]
<marex>
vagrantc: reading now
<marex>
vagrantc: ugh, it sounds so ominous ... but all it does is it uses u-boot console ... indeed
<marex>
vagrantc: this is really up to the device vendor to lock the device down, including disabling console access and such
pitillo has joined #u-boot
<Tartarus>
I've already complained to MITRE about that one, it's against a 20 year old (almost literally, Aug 14 2005, iirc) version of U-Boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
clamor has quit [Ping timeout: 248 seconds]
<vagrantc>
marex, Tartarus: thanks for confirmation :)