This blog post is all about my experiences at securing web@Zap day-1
I love to explore web to learn some new stuff. Infact, most of the time, I deal with learning geeky computer stuff and went mad with a few terminologies like Hacking, Click jacking, XSS scripting, spamming, phishing, cookie stealing and tried a lot to learn them but didn’t get any perfect resource. Am still trying to learn these techinques to call myself a hacker( 😛 just kiding).
Soon i get into mozilla, I checked many mozillian profiles to get an idea and to make myself contribute for mozilla. Meanwhile, I meet Mozilla Rep, Sumanth Damarla at FSA Boot camp, bangalore. After the event, I was in touch with him on facebook, following his activities and i really astonished seeing his Mozillian profile, [Sumanth Damarla- OWASP, ZAP contributor at MWOS].From that day, i was really very curious to learn some basics about OWASP. Luckily, I got an event invite “Securing web @ZAP” which i dreamed of learning. Unfortunately, i cant attend for full 4weekend workshops but attended the first weekend to learn basics.
As soon as i reached Collab house,Hyderabad, Sumanth already started introduction to the workshop. (I was late for half an hour though 😛 😀 ). Then sumanth started explaining about OWASP and ZAP from scratch. The session went on as follows.
*> Introduction of the Attendees:
I’ve been to a few events at collab house.This time, I felt amazing meeting with many new Tech savvys and ZAP enthusiasts.
*> Brief description about ZAP workshop
*> Types of vulnerabilities (OWASP top ten):
Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.
A2-Broken Authentication and Session Management
Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.
A3-Cross-Site Scripting (XSS)
XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
A4-Insecure Direct Object References
A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.
Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
A6-Sensitive Data Exposure
Many web applications do not properly protect sensitive data, such as CREDIT CARDS, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
A7-Missing Function Level Access Control
Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
A8-Cross-Site Request Forgery (CSRF)
A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
A9-Using Components with Known Vulnerabilities
Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.
A10-Unvalidated Redirects and Forwards
Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.
*> Small Assessment:
worksheets are distributed to each attendee to self assess themselves about basics in security project.
After a very good Introductory session, we finally had a group picture with several ZAP enthusiasts along with organisers Sumanth, Sanjay and Sudarshan. It was an amazing experience to meet new people and learn new technology. Excited to learn more about it on DAY-2.