You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using IoTSeeker to scan for devices with default credentials on our
network we noticed that while IoTSeeker does work with basic auth but when
using forms it appears to not set the content-type HTTP header. IoTSeeker
then responds with 'default password was found' regardless of the
credentials passed to it from some devices such as AMX devices.
Using Wireshark we can see that IoTSeeker does not set the content-type
header and form variables are not set in the server response.
Using Wireshark with curl we confirmed that the content-type header is
(automatically) set and form variables are correctly set in the server
response.
I may have missed something in the devices.cfg?
"AMX":{
"devTypePattern": [["header", "server"], ["regex", "^The Knopflerfish"]],
"nextUrl": ["string", "/web/root/login.xml"],
"auth": ["form","", "userName=administrator&password=password", "body",
"!substr", "Invalid user name or password"]
},
Kind regards,
Elliott
The text was updated successfully, but these errors were encountered:
Hi,
While using IoTSeeker to scan for devices with default credentials on our
network we noticed that while IoTSeeker does work with basic auth but when
using forms it appears to not set the content-type HTTP header. IoTSeeker
then responds with 'default password was found' regardless of the
credentials passed to it from some devices such as AMX devices.
Using Wireshark we can see that IoTSeeker does not set the content-type
header and form variables are not set in the server response.
Using Wireshark with curl we confirmed that the content-type header is
(automatically) set and form variables are correctly set in the server
response.
I may have missed something in the devices.cfg?
"AMX":{
"devTypePattern": [["header", "server"], ["regex", "^The Knopflerfish"]],
"nextUrl": ["string", "/web/root/login.xml"],
"auth": ["form","", "userName=administrator&password=password", "body",
"!substr", "Invalid user name or password"]
},
Kind regards,
Elliott
The text was updated successfully, but these errors were encountered: