Awesome
"Word Lists" for Software Security Test Cases
<!-- <span style="color: red">WARNING<b>:</b></span> REPOSITORY IS NEARING 1GB -->Word lists, Dictionary Files, Attack Strings, Miscellaneous Datasets and Proof-of-Concept Test Cases With a Collection of Tools for Penetration Testers
- <a href="#intro">Brief Introduction to
werdlists
</a> - <a href="#inspire">Inspiration Taken from Similar Projects</a>
- <a href="#unique">Unique Features Only Available With
werdlists
</a>
- <a href="#unique">Unique Features Only Available With
- <a href="#repo">Repository Directory Hierarchy and Structure</a>
- <a href="#naming">Naming Scheme, Syntax and Meaning</a>
- <a href="#contents">Folder Names and Description of Contents</a>
<a name="intro"></a>Brief Introduction to werdlists
:scissors:
This project is a collection of word lists--they are mostly whitespace-delimited
or line-based. Although the passes-dicts
folder contains inputs for password cracking,
overall the files amassed here are intended to be useful in facilitating
the creation of insecure program state (with the help of a black-box fuzzer or scanning
tool.) The vast majority of files are simply ASCII with the UNIX
style newline. Beware that this project does not attempt in any way to be minimalist or lack verbosity!
<a name="inspire"></a>Inspiration Taken From Similar Projects :thought_balloon:
werdlists
is very similar to fuzzdb
and
SecLists
. SecLists
is maintained by my former colleague at IOActive, Daniel Miessler.
Admittedly, werdlists
is quite similar in mission as it's a centralized attack strings
and input data resource. Regardless, werdlists
expands on a number of concepts: it has its own unique style, organization,
original hand-crafted contents, dataset creation/management/validation scripts, scanner springboards, etc.
<a name="unique"></a>Unique Features Only Available With werdlists
:100:
werdlists
cross-references between the code repositories of third-party scanners and its own datasets that each tool will benefit from.
Moreover, there are specialized parsing scripts exclusive to werdlists
that extract results produced through pairing test tools with its own data. Output strings are gathered from those results and fed back into the test tools. In other words, there are a number of interactive and/or
tunable feedback loops implemented. Quite a few of the werdlists
data files were created this way.
<a name="repo"></a>Repository Directory Hierarchy and Structure :nut_and_bolt:
The scripts
folder consists of shell scripts used for repository maintenance.
There is a sub-directory of scripts
called init
where scripts that initialize data files are stored. If a script filename stored in init
contains
two dashes, then it's output should reflect the contents of the associated data file. For example, compare manpages-environ
and clib-package-names
. All scripts were written using bash syntax.
The contrib
folder is for storing scripts contributed via pull request and the utils
folder contains utilities that aren't necessarily specific to the werdlists
project, such as scripts for managing any wordlist file.
Other data files were manually composed by hand and a small handful were created by recycling output strings back into input parameter lists, i.e. dirbdirs-feedback
The tools
folder lists security tools that the datasets contained in this repository can be provided as input for.
Individual folders are detailed in the <a href="#contents">Folder Names and Description of Contents</a> section below.
All files in each dataset directory are detailed in the local README.md
file for that folder (as opposed to the global README.md
in the root directory being read now.)
<a name="naming"></a>Naming Scheme, Syntax and Meaning :speech_balloon:
Most files have the *.txt
extension signifying the text/plain
MIME type
Often used formats besides plain text include: Comma-Separated Values (text/csv
),
Extended Markup Language (application/xml
),
Hyper Text Markup Language (application/html
), etc.
Any file that is larger than 1MB uncompressed will be compressed with xz
according to the commands in the scripts/xzlarge-files
bash script. Other file extensions in use are:
*.ans
, *.asc
, *.bin
, *.c
, *.conf
, *.cpp
, *.csv
, *.html
, *.inf
, *.ini
, *.json
, *.md
, *.rpz
, *.rst
, *.sh
, *.txt
, *.xml
, *.yaml
, *.yml
, *.zip
, and *.zone
.
<a name="contents"></a>Folder Names and Description of Contents :clipboard:
Folder Name | Description of Contents |
---|---|
apple-paths | :rocket: Pathnames found on MacOS file systems |
apple-data | :apple: Data identifiers and such from Apple's MacOS operating system |
arpa-headers | :email: Header fields transmitted over RFC2822 style protocols like SMTP |
ascii-art | :art: "Low bit" a.k.a. 7-bit ASCII art items without control characters |
biology-info | :microscope: Reference information useful in the study of biological issues |
browser-data | :door: Data related to GUI browser software like Chrome, FireFox, etc. |
cert-data | :scroll: Information commonly utilized by cryptographic certificate materials |
char-encodes | :ideograph_advantage: Various character encodings provided by different locales/charsets |
char-sequence | :black_nib: various character sequences modeled after ctype.h |
chat-data | :open_mouth: Additional data on IRC, XMPP and other such messaging protocols |
cipher-data | :blowfish: Data denoting or used by cryptographic algorithm implementations |
cmd-usage | :hammer: Help text shown in a terminal when attempting to execute CLI programs |
code-keywords | :coffee: Computer language identifiers, reserved words and similar syntax |
cpu-arch | :factory: Low-level computer architecture and hardware subjects |
crypt-output | :sparkles: Cipher text string outputs created by cryptographic hash functions |
database-strs | :floppy_disk: Strings often encountered when working with database software |
dns-domains | :globe_with_meridians: A list of domains that may have been found in the live DNS tree at one point |
dns-hostnames | :flashlight: The host name part of an FQDN |
dns-records | :ticket: Data specific to RR's in the DNS system |
dns-servers | :battery: Data provided to, produced by or related to DNS name servers |
dns-toplevel | :top: TLD's or Top Level Domains in the uppermost part of the DNS hierarchy |
environ-vars | :tent: Environment variable names, settings, etc. |
exploit-info | :8ball: Technical information on exploitation of security vulnerabilities |
file-extens | :anchor: Stuff on Filename extensions, i.e. the part after the dot |
file-specs | :file_folder: File format specifications as distributed by vendor(s)/author(s) |
ftp-data | :outbox_tray: Various FTP datum from RFC's and elsewhere |
glibc-data | :gear: Data taken from the source code of the GNU C Library |
html-words | :keyboard: Words not uncommon to come across when parsing HTML dialects |
http-agents | :flags: Software version banners for HTTP User Agents also known as browsers |
http-headers | :cookie: Header fields sent in requests/responses by browser/server software |
http-methods | :arrow_forward: Names Request methods browsers send in the first line of HTTP |
http-params | :abcd: Parameters browsers sometimes send when requesting server URI paths |
http-security | :closed_lock_with_key: HTTP security info such as Content Security Policy |
http-servers | :office: Information related to the usage of web server software |
http-status | :slot_machine: Numeric HTTP status codes in server reply as RFC7231 specifies |
inet-addrs | :electric_plug: Numeric Internet addresses a.k.a. IP addresses--mostly version 4 |
inet-routes | :cloud: Data useful in the maintenance and use of an Internet routing table |
inet-services | :fountain: Lists of Internet protocols/daemons--similar to /etc/services |
infosec-people | :neckbeard: Noteworthy individuals known from information security communities |
iso-codes | :heavy_check_mark: Codes, numbers and such as standardized by ISO |
java-data | :sunny: Data found in or related to source code of programs written with Java |
linux-data | :keycap_ten: Data identifiers and such from the Linux operating system |
linux-paths | :paperclips: Pathnames found on file systems created by Linux installations |
malware-iocs | :skull: IOC for identification of malware infections |
mobile-devs | :iphone: Mobile device development for "handheld" form factors |
net-attacks | :hotsprings: Info about attacks on telecommunications and Internetworks |
net-ifaces | :desktop_computer: Detailed information which can be extracted from network interfaces |
ntfs-paths | :open_file_folder: File paths expected to be seen in NTFS folders |
owasp-data | :honeybee: Data from or for OWASP |
passes-dicts | :key: Dictionary files for brute-force attacks against account passwords |
passes-sites | :unlock: Hashed or unencrypted passwords that were publicized after the breach of a well-known site |
perl-data | :camel: Data often seen in PERL (Practical Extraction and Report Language) |
php-data | :page_facing_up: Files containing information about the PHP programming language |
postal-data | :mailbox_with_mail: United States Postal Service information |
python-data | :snake: Data used by the Python scripting language interpreter at runtime |
radio-data | :radio: Things commonly used in radio frequency transmissions |
regex-data | :speech_balloon: Regular expression patterns used to launch/detect attacks |
ruby-data | :gem: Data typically seen within the syntax of the Ruby scripting language |
search-dorks | :mag_right: General purpose search-engine queries likely to find insecure sites |
smtp-messages | :envelope: Messages (i.e. signatures, auto-replies, etc.) sent by SMTP servers |
soap-messages | :incoming_envelope: SOAP (Simple Object Access Protocol) messages |
social-data | :eyes: Sociological or social media related data sets including logins and user names |
software-strs | :minidisc: Strings describing software engineering, programming languages, etc. |
string-enums | :ferris_wheel: Enumerations of values that aren't too terribly unusual |
system-admin | :necktie: System administration and BOFH related materials |
system-notices | :warning: Disclaimer/warning messages shown by networked computer systems |
telco-data | :telephone_receiver: Voice telecommunications technologies: POTS, PCS, VoIP, SMS etc. |
text-files | :pushpin: zine articles and such like those archived at Jason Scott's textfiles.com |
text-words | :pencil2: Lists of words likely to be found in an actual hard copy dictionary |
top-secret | :alien: Files and/or data related to documents that were/are classified |
unicode-data | :symbols: Unicode character usage and representation |
unix-data | :shell: Data associated with various flavors of the UNIX OS and its clones |
unix-paths | :file_cabinet: File path names found in various UNIX file systems |
uri-attacks | :boom: Malicious URI materials specially crafted for attack targets |
uri-schemes | :paperclip: Lists containing references for URI schemes (part before colon) |
uri-data | :link: Universal Resource Identifier related data |
vuln-data | :bar_chart: Information about security vulnerabilities found in server software |
webapp-attacks | :syringe: Proof-of-concept samples demonstrating attacks against web applications |
webapp-data | :briefcase: Data associated with applications hosted on web servers |
webapp-dirs | :bookmark_tabs: Directories related to applications running on a web server |
webapp-files | :card_index: Files related to applications running on a web server |
webapp-paths | :surfer: Path names related to applications running on a web server |
webapp-words | :thought_balloon: Words related to applications running on a web server |
web-sites | :earth_americas: Addresses to and/or information on significant WWW sites |
wifi-networks | :satellite: IEEE 802.11 Wi-Fi network information |
windows-data | :briefcase: Data only found within the Microsoft Windows series of OSes |
ans asc bin c conf cpp csv html inf ini json md rpz rst sh txt xml yaml yml zip zone