hakip2host icon indicating copy to clipboard operation
hakip2host copied to clipboard

unexpected errors

Open marcelo321 opened this issue 2 years ago • 2 comments

I was using the tool against same IPs like this:

cat ips | hakip2host > results

But I noticed some unexpected errors while it was running:

2022/04/25 04:50:12 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:50:12 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:50:12 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:50:27 Unsolicited response received on idle HTTP channel starting with "Unauthorized access\n"; err=<nil>
2022/04/25 04:50:32 Unsolicited response received on idle HTTP channel starting with "<!DOCTYPE html>\n<html>\n  <head>\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n    <meta charset=\"utf-8\">\n    <title>Heroku | Application Error</title>\n    <style media=\"screen\">\n      html,body,iframe {\n        margin: 0;\n        padding: 0;\n      }\n      html,body {\n        height: 100%;\n        overflow: hidden;\n      }\n      iframe {\n        width: 100%;\n        height: 100%;\n        border: 0;\n      }\n    </style>\n  </head>\n  <body>\n    <iframe src=\"//www.herokucdn.com/error-pages/no-such-app.html\"></iframe>\n  </body>\n</html>\n"; err=<nil>
2022/04/25 04:51:02 Unsolicited response received on idle HTTP channel starting with "<!DOCTYPE html>\n<html>\n<head>\n <meta charset=\"UTF-8\">\n</head>\n<body>\n<h1>Burp Collaborator Server</h1>\n<p>Burp Collaborator is a service that is used by <a href=\"https://portswigger.net/burp/\">Burp Suite</a> when testing web applications for security\nvulnerabilities. Some of Burp Suite's tests may cause the application being\ntested to interact with the Burp Collaborator server, to enable Burp Suite\nto detect various security vulnerabilities.\n</p><p>The Burp Collaborator server does not itself initiate any interactions with\nany system, and only responds to interactions that it receives from other\nsystems.\n</p><p>If you are a systems administrator and you are seeing interactions with the\nBurp Collaborator server in your logs, then it is likely that someone is\ntesting your web application using Burp Suite. If you are trying to identify\nthe person responsible for this testing, you should review your web server\nor applications logs for the time at which these interactions were initiated\nby your systems.\n</p><p>For further details about Burp Collaborator, please see the <a href=\"https://portswigger.net/burp/documentation/collaborator/\">full documentation</a>.</p></body>\n</html>"; err=<nil>
2022/04/25 04:51:06 Unsolicited response received on idle HTTP channel starting with "<!DOCTYPE html>\n<html>\n<head>\n <meta charset=\"UTF-8\">\n</head>\n<body>\n<h1>Burp Collaborator Server</h1>\n<p>Burp Collaborator is a service that is used by <a href=\"https://portswigger.net/burp/\">Burp Suite</a> when testing web applications for security\nvulnerabilities. Some of Burp Suite's tests may cause the application being\ntested to interact with the Burp Collaborator server, to enable Burp Suite\nto detect various security vulnerabilities.\n</p><p>The Burp Collaborator server does not itself initiate any interactions with\nany system, and only responds to interactions that it receives from other\nsystems.\n</p><p>If you are a systems administrator and you are seeing interactions with the\nBurp Collaborator server in your logs, then it is likely that someone is\ntesting your web application using Burp Suite. If you are trying to identify\nthe person responsible for this testing, you should review your web server\nor applications logs for the time at which these interactions were initiated\nby your systems.\n</p><p>For further details about Burp Collaborator, please see the <a href=\"https://portswigger.net/burp/documentation/collaborator/\">full documentation</a>.</p></body>\n</html>"; err=<nil>
2022/04/25 04:51:07 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:51:07 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:51:07 Unsolicited response received on idle HTTP channel starting with "The requested URL was not found on this server"; err=<nil>
2022/04/25 04:51:20 Unsolicited response received on idle HTTP channel starting with "<!DOCTYPE html>\n<html>\n  <head>\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n    <meta charset=\"utf-8\">\n    <title>Heroku | Application Error</title>\n    <style media=\"screen\">\n      html,body,iframe {\n        margin: 0;\n        padding: 0;\n      }\n      html,body {\n        height: 100%;\n        overflow: hidden;\n      }\n      iframe {\n        width: 100%;\n        height: 100%;\n        border: 0;\n      }\n    </style>\n  </head>\n  <body>\n    <iframe src=\"//www.herokucdn.com/error-pages/no-such-app.html\"></iframe>\n  </body>\n</html>\n"; err=<nil>
2022/04/25 04:51:20 Unsolicited response received on idle HTTP channel starting with "<!DOCTYPE html>\n<html>\n  <head>\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n    <meta charset=\"utf-8\">\n    <title>Heroku | Application Error</title>\n    <style media=\"screen\">\n      html,body,iframe {\n        margin: 0;\n        padding: 0;\n      }\n      html,body {\n        height: 100%;\n        overflow: hidden;\n      }\n      iframe {\n        width: 100%;\n        height: 100%;\n        border: 0;\n      }\n    </style>\n  </head>\n  <body>\n    <iframe src=\"//www.herokucdn.com/error-pages/no-such-app.html\"></iframe>\n  </body>\n</html>\n"; err=<nil>
2022/04/25 04:51:25 Unsolicited response received on idle HTTP channel starting with "Nothing here, move along"; err=<nil>

I am not sure if is should be considered normal or not. Where are this errors coming from? These are output to stderr

marcelo321 avatar Apr 25 '22 05:04 marcelo321

Same going on with me, I'll be waiting for an answer. Forgot to mention, that I had found a quick way of avoiding this, which would be redirecting the standard error to null.

  • Like so:

$ hakip2host 2>/dev/null

RodricBr avatar Jul 30 '22 23:07 RodricBr

I have no idea what's causing this sorry!

hakluke avatar May 18 '23 21:05 hakluke