Let’s Talk about Web Security : OWASP Top 10 Security Risks 2017

OWASP-top-10-Cover

Premise:

In today’s times where we see new frameworks and libraries being launched every other day, it’s hard to keep up. And it has become even harder to make developers dedicate time for security. In case of frameworks like Angular many security risks are handled within the frameworks. So, that saves some work for the developers. However, that also makes developers unaware of these risks more often than not.

Today we’re going to talk about the Top 10 web security risks determined based on data collected from reported incidences and community opinions. OWASP – The Open Web Application Security Project, is an open community dedicated to enabling organizations to develop, purchase, and maintain applications and APIs that can be trusted.

What are these risks and why should I care?

Attackers can potentially use many different paths through your application to do harm to your business or organization. Each of these paths represents a risk that may, or may not, be serious enough to warrant attention. Sometimes these paths are trivial to find and exploit, and sometimes they are extremely difficult. Similarly, the harm that is caused may be of no consequence, or it may put you out of business.

OWASP releases the list of top 10 security risks every 3-4 years. Last they released the list in 2017, which was an update on the list released back in 2013. Here are the top 10 risks as per OWASP top 10, 2017:

OWASP-TOP-10

1. A1:2017-Injection:

Injection flaws, such as SQL, NoSQL, 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.

2. A2:2017-Broken Authentication:

Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently.

3. A3:2017-Sensitive Data Exposure:

Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser.

4. A4:2017-XML External Entities (XXE):

Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks.

5. A5:2017-Broken Access Control:

Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access to other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc.

6. A6:2017-Security Misconfiguration:

Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched and upgraded in a timely fashion.

7. A7:2017-Cross-Site Scripting (XSS):

XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. 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.

8. A8:2017-Insecure Deserialization:

Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.

9. A9:2017-Using Components with Known Vulnerabilities:

Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts.

10. A10:2017-Insufficient Logging&Monitoring:

Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Conclusion:

It’s easy to get carried away with the pace at which web development happens today. But take a pause and make sure your application is not prone to these risks. Obviously, these are just the top 10 risks and covering these does not mean you’re safe. But covering these should be a good starting. Code Safe!

Download the full PDF release of OWASP TOP 10 Security Risks by subscribing to our newsletter.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.