=begin Copyright 2010-2022 Ecsypno This file is part of the Arachni Framework project and is subject to redistribution and commercial restrictions. Please see the Arachni Framework web site for more information on licensing and terms of use. =end # Looks for sensitive common files on the server. # # @author Tasos "Zapotek" Laskos class Arachni::Checks::CommonFiles < Arachni::Check::Base def self.filenames @filenames ||= read_file( 'filenames.txt' ) end def run return if page.code != 200 path = get_path( page.url ) return if audited?( path ) self.class.filenames.each { |file| log_remote_file_if_exists( path + file ) } audited( path ) end def self.info { name: 'Common files', description: %q{Tries to find common sensitive files on the server.}, elements: [ Element::Server ], author: 'Tasos "Zapotek" Laskos ', version: '0.2.4', exempt_platforms: Arachni::Platform::Manager::FRAMEWORKS, issue: { name: %q{Common sensitive file}, description: %q{ Web applications are often made up of multiple files and directories. It is possible that over time some files may become unreferenced (unused) by the web application and forgotten about by the administrator/developer. Because web applications are built using common frameworks, they contain common files that can be discovered (independent of server). During the initial recon stages of an attack, cyber-criminals will attempt to locate unreferenced files in the hope that the file will assist in further compromise of the web application. To achieve this they will make thousands of requests using word lists containing common filenames. The response headers from the server will then indicate if the file exists. Arachni also contains a list of common file names which it will attempt to access. }, references: { 'Apache.org' => 'http://httpd.apache.org/docs/2.0/mod/mod_access.html' }, tags: %w(common path file discovery), severity: Severity::LOW, remedy_guidance: %q{ If files are unreferenced then they should be removed from the web root and/or the application directory. Preventing access without authentication may also be an option and can stop a client from being able to view the contents of a file, however it is still likely that the directory structure will be able to be discovered. Using obscure file names is implementing security through obscurity and is not a recommended option. } } } end end