Difference between revisions of "OWASP Vicnum Project"

Q1 Anything I need to set up vicnum?

There are help folder in the downloads and a pdf manual. Basically set up the database, make sure the apache modules are loaded and modify the http config file to find the perl code in the cgi-bin folder.

Q2 Is there a way to make the challenges harder or easier?

Sure. Some suggestions are in the help file, one of them of course is to delete the help file. You can also modify the backdoors, allow indexing of folders, or change the encoding of hidden fields.

Q3 Is there more to it than just technical challenges?

Absolutely. In hacking a web application looking at the nature of the app or examining the so-called business logic is always a good idea. So looking for the back doors and hidden files is definitely a goal here.

Volunteers

Vicnum is developed by a worldwide team of volunteers. The primary contributors to date have been:

• Nicole Becher
• Mordecai Kraushar

Others

Vicnum has been demonstrated at many chapter events, many attendees have provided feedback afterwards. In particular a big shout out to Daniel Zabib, Anthony Martini and Albert Fong who helped customize Vicnum applications for the APPSECUSA conference.

The Vicnum Project is affiliated with the Brooklyn OWASP chapter.

The vulnerable API !

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

Injection

Verbosity

Transport Encryption Denial of Service

Insecure Direct Object References

Unrestricted File Uploads

Involvement in the development and promotion of Vicnum is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

• Coming up with a name (and maybe themes for a vulnerable API program)

Projects/OWASP Vicnum Project