[issue18564] Integer overflow in the socket function parsing a Bluetooth address

STINNER Victor added the comment: Hum, maybe I'm just confused by "integer overflow". To me, "integer overflow" means that an operation goes out of the bounds of a C integer type. But here, the problem is more than the parser accepts invalid Bluetooth addresses? Please use a better title tha

[issue18564] Integer overflow in the socket function parsing a Bluetooth address

Steve Dower added the comment: According to a couple of scanf docs I found, the '%x' format expects to write into unsigned int*, just as we already do. So it shouldn't be possible to overflow there. The following line (or-ing all the values and checking that it's less than 256) handles the

[issue18564] Integer overflow in the socket function parsing a Bluetooth address

Serhiy Storchaka added the comment: Seconded Viktor's question. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-l

[issue18564] Integer overflow in the socket function parsing a Bluetooth address

Change by STINNER Victor : -- title: Integer overflow in socketmodule -> Integer overflow in the socket function parsing a Bluetooth address versions: +Python 3.7, Python 3.8 ___ Python tracker _