This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Project Information:template Vicnum Project"
From OWASP
(→Road Map and Getting Involved) |
(→Road Map and Getting Involved) |
||
Line 141: | Line 141: | ||
API’s are everywhere! Mobile & web applications applications, cloud services, the Internet of Things and embedded devices are all communicating via API’s. A vulnerable API can be just as destructive as a vulnerable web application. So, how do you test an API? The vulnerable API has a number of serious issues including many of the classic OWASP Top 10 vulnerabilities. This release is meant for pen testers, breakers and developers and will demonstrate some of the common flaws that are found in API’s such as: | API’s are everywhere! Mobile & web applications applications, cloud services, the Internet of Things and embedded devices are all communicating via API’s. A vulnerable API can be just as destructive as a vulnerable web application. So, how do you test an API? The vulnerable API has a number of serious issues including many of the classic OWASP Top 10 vulnerabilities. This release is meant for pen testers, breakers and developers and will demonstrate some of the common flaws that are found in API’s such as: | ||
Authentication | Authentication | ||
+ | ---- | ||
Injection | Injection | ||
+ | ---- | ||
Verbosity | Verbosity | ||
+ | ---- | ||
Transport Encryption | Transport Encryption | ||
Denial of Service | Denial of Service | ||
+ | ---- | ||
Insecure Direct Object References | Insecure Direct Object References | ||
+ | ---- | ||
Unrestricted File Uploads | Unrestricted File Uploads | ||
− | + | ||
Revision as of 18:44, 13 May 2016
Vicnum was introduced in 2009 as new CTFs have been introduced releases have changed. Recent release upgrades are:
V1.5 (December 2013) Cyclone, a vulnerable Ruby on Rails Application
V1.6 (June 2014) Breaking Bad XXE Exploit
V1.7 (December 2015) Basic CTF to parse a pcap
V2.0 will be introduced in May 2016 and will include an intentionally vulnerable API.