wapiti 2.2.1+dfsg-1 source package in Ubuntu
Changelog
wapiti (2.2.1+dfsg-1) unstable; urgency=low * QA upload. [ Arthur de Jong ] * New upstream release (Closes: #550072). * Orphaning package (See: #700556). * Drop no longer relevant recommends. * Install wapiti-getcookie and wapiti-lswww commands. * Update patches (drop most because no longer relevant). * Install upstream manual page. * Provide a get-orig-source target that drops the unused and non-free json.js from the upstream tarball. * Don't install bundled BeautifulSoup and httplib2 and instead use the system ones. * Disable the built-in Nikto plugin because of licensing issues of the used database file. * Install a README.Debian that explains the differences from upstream. * Update debian/copyright file. * Update debian/watch file. * Update to Standards-Version to 3.9.4. * Update package description. [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. -- Arthur de Jong <email address hidden> Fri, 28 Jun 2013 15:14:56 +0200
Upload details
- Uploaded by:
- Debian QA Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian QA Group
- Architectures:
- all
- Section:
- python
- Urgency:
- Low Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Trusty | release | universe | python |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
wapiti_2.2.1+dfsg-1.dsc | 1.2 KiB | 1766f09ac95ccbeb4d00c29ed8b110400f4c2c4a90f40f0d4cbe21fca77df96a |
wapiti_2.2.1+dfsg.orig.tar.gz | 412.9 KiB | c8ed0f93206e840c73c3bd3afa17ed70ebe6e5f784a955ab0b7050ddeb5519cf |
wapiti_2.2.1+dfsg-1.debian.tar.gz | 8.6 KiB | 2b372e4b83ef50955ad31251c0e5f9105ff7ef83b986255cd6e941846130321f |
Available diffs
- diff from 1.1.6-4 to 2.2.1+dfsg-1 (241.1 KiB)
No changes file available.
Binary packages built by this source
- wapiti: web application vulnerability scanner
Wapiti allows you to audit the security of your web applications.
It performs "black-box" scans, i.e. it does not study the source code of the
application but will scan the web pages of the deployed web applications,
looking for scripts and forms where it can inject data.
Once it gets this list, Wapiti acts like a fuzzer, injecting payloads to see
if a script is vulnerable.
.
Wapiti can detect the following vulnerabilities:
- file handling errors (local and remote include/require, fopen,
readfile...)
- database injection (PHP/JSP/ASP SQL Injections and XPath Injections)
- XSS (Cross Site Scripting) injection
- LDAP injection
- command execution detection (eval(), system(), passtru()...)
- CRLF injection (HTTP response splitting, session fixation...)