3 ms·
The original bug report said "very highly unlikely it's technically remotely exploitable", but it seems that may not be the case. "Working with the exploit, it
by chair6 13y ago
The original bug report said "very highly unlikely it's technically remotely exploitable", but it seems that may not be the case.
"Working with the exploit, its trivial to get a working remote exploit to work, below is a simple rewritten RCE from the exploit PoC": https://www.trustedsec.com/february-2014/python-remote-code-execution-socket-recvfrom_into/ https://www.trustedsec.com/february-2014/python-remote-code-...
- makomk 13y agoIt's only remotely exploitable in Python applications that use socket.recvfrom_into in a particular, unsafe way. I'm not sure how many are out there in practice.
- teddyh 13y agoYou are reading it wrong. The original bug report said “I will attach patches for 3.4 and 2.7, I'm not familiar with the backporting procedure to go further but all versions since 2.5 have this bug and while very highly unlikely it's technically remotely exploitable.” So if one were to insert commas in the appropriate places, it becomes “and, while very highly unlikely, it's technically remotely exploitable.”. So the original bug report did concede that, while the bug itself is very unlikely, the bug is remotely exploitable.