How to and Uses of Nikto

Nikto Web Scanner is a Web server scanner that tests Web servers for dangerous files or common gateway interfaces, outdated server software and other problems. It performs generic and server type specific checks while capturing and printing any cookies received. Nikto also checks for server configuration items such as the presence of multiple index files, HTTP server options, and will attempt to identify installed web servers and software. Scan items and plugins are frequently updated and can be automatically updated. The Nikto code itself is open source, but the data files it uses to run the programs are not. The code can also be found on GitHub.

Nikto is not designed as a stealthy tool. It will test a web server in the quickest time possible, and is obvious in log files or to an IPS/IDS.

Not every check is a security problem, though most are. There are some items that are “info only” type checks that look for things that may not have a security flaw, but the webmaster or security engineer may not know are present on the server. These items are usually marked appropriately in the information printed. There are also some checks for unknown items which have been seen scanned for in log files.


Features
Here are some of the major features of Nikto.

  • SSL Support (Unix with OpenSSL or Windows with ActiveState’s Perl/NetSSL)
  • Full HTTP proxy support
  • Checks for outdated server components
  • Save reports in plain text, XML, HTML, NBE or CSV
  • LibWhisker‘s IDS encoding techniques
  • Host authentication with Basic and NTLM
  • Subdomain guessing
  • Apache and cgiwrap username enumeration
  • Mutation techniques to “fish” for content on web servers
  • Scan tuning to include or exclude entire classes of vulnerability
    checks
  • Guess credentials for authorization realms (including many default id/pw combos)
  • Authorization guessing handles any directory, not just the root
    directory
  • Enhanced false positive reduction via multiple methods: headers,
    page content, and content hashing
  • Reports “unusual” headers seen
  • Save full request/response for positive tests
  • Maximum execution time per target
  • Logging to Metasploit

To use, first boot up the Kali Linux and typing the command below:

nikto -h [address]

Nikto will return a lot of results, some of which are PHP version, XSS vulnerabilities, and server OS. If, at the end of the scan, Nikto finds vulnerabilities, it will return OSDVB codes. To check what the codes mean, you can visit www.osdvb.org.

 

Source: https://cirt.net/Nikto2; https://en.wikipedia.org/wiki/Nikto_Web_Scanner

Hacking with Google

Google Hacking, a.k.a. Google Dorking, is a computer hacking method that uses the Google search engine and other Google applications to find, in general, one or both of the following: software vulnerabilities and   misconfigurations by websites. On top of that, search queries on Google can be used to gather information for arbitrary or individual targets, discover error messages that disclose sensitive information, or seeking files containing credentials and other sensitive data. The search can also be limited to specific pages on a specific site, or it can search for specific information across all websites, giving a list of sites that hold said information.

Google hacking itself can be traced back to 2002. Johnny Long, an American computer security expert, author, and public speaker, began to uncover “unique” Google search queries. He dubbed this list of “unique” queries Google Dorks, and it grew into a large dictionary, before eventually converted into a database. Currently, many hackers also employ other search engines beside Google, such as Bing and Shodan. In fact, the latter is more oriented for searching crucial data, but the comprehensiveness of the results may not be as high as other, more widely-used search engines.

For instance, the following search query will list SQL files (filetype:sql) available that have been indexed by Google on websites where directory listing is enabled (intitle:"index of"). The database can be accessed through https://www.offensive-security.com/community-projects/google-hacking-database/ or https://www.exploit-db.com/google-hacking-database/.

It is possible to hide some of your information from Google, therefore preventing public viewing. One such method is to directly ask Google to uncache your information. To do that, one can visit https://www.google.com/remove.html and follow the steps from there.

Source: https://www.acunetix.com/websitesecurity/google-hacking/; https://searchsecurity.techtarget.com/definition/Google-hacking.