Classification of PVS-Studio warnings according to OWASP Top 10 Web Application Security Risks

OWASP Top 10 is the rating of ten most critical web application security risks that is based on a general consensus of security experts from around the world. The ranking in the rating is based on severity of listed potential security threats, the frequency of these threats and on the magnitude of potential damage that they can inflict. The goal of OWASP Top 10 project is to provide developers and security specialists with information that can help them identify, counteract and promptly rectify security risks to the applications they are developing.

Every few years OWASP Top 10 rating is updated to reflect the most relevant application security threats. PVS-Studio classifies its diagnostic rules in accordance with OWASP Top 10 version 2017.

CategoryPVS-Studio Rule
A1 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.V5009 - Unchecked tainted data is used in expression.
A2 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.Coming soon.
A3 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.V5305 - Storing credentials inside source code can lead to security issues.
V5601 - Storing credentials inside source code can lead to security issues.
A4 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.Coming soon.
A5 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 other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc.Coming soon.
A6 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/upgraded in a timely fashion.Coming soon.
A7 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.Coming soon.
A8 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.Coming soon.
A9 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.Coming soon.
A10 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.V5002 - An empty exception handler. Silent suppression of exceptions can hide the presence of bugs in source code during testing.
V5003 - The object was created but it is not being used. The 'throw' keyword could be missing.
V5008 - Classes should always be derived from std::exception (and alike) as 'public'.
V5301 - An exception handling block does not contain any code.
V5302 - Exception classes should be publicly accessible.
V5303 - The object was created but it is not being used. The 'throw' keyword could be missing.
V5602 - The object was created but it is not being used. The 'throw' keyword could be missing.
V5603 - The original exception object was swallowed. Stack of original exception could be lost.
V5606 - An exception handling block does not contain any code.
V5607 - Exception classes should be publicly accessible.

Bugs Found

Checked Projects
Collected Errors
14 526
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site. Learn More →