The most common vulnerabilities of web applications

According to statistics maintained by theOpen Web Application Security Project (OWASP), the ten most common security errors can be distinguished. The graphic below shows how often veracode, a web application security research organization, detects these vulnerabilities during a preliminary risk assessment.

OWASP Top 10 Vulnerability Detection Rate during Veracode Initial Risk Assessment The vulnerability detection rate from the OWASP Top 10 list during veracode's initial risk assessment. Source: [Veracode]

The most common vulnerabilities cited above according to the OWASP are:

  1. Susceptibility of injecting untrusted data into a code interpreter as part of a command orquery (SQLi, OS, XXE, LDAP). An attacker could outsmart the interpreter to execute unscheduled commands or gain access to data without proper authorization.
  2. Incorrectly implemented mechanisms for authenticity and session management. This allows the attacker to compromise passwords, keys, session tokens, or hijack the identity of another application user.
  3. Cross-site scripting (XSS)is an attack that injects JavaScript into the content of the attacked page. It can be used to hijack a user's session, redirect to a dangerous user site, or social engineering attacks.
  4. Broken access control mechanisms regarding what permissions and resources a system user has access to. An attacker could exploit this vulnerability to gain access to unauthorized functionality or sensitive data, as well as to gain access to other users' accounts.
  5. Incorrect security settings – to properly secure the system, the appropriate settings are defined and implemented for the application, framework, application server, database server, platform, etc. In addition, the software should be updated regularly.
  6. Sharing sensitive data – Many web applications and APIs do not properly protect sensitive data such as financial, medical or personal data. An attacker can steal or modify such poorly protected information and use it to fraud on a credit card, steal identity or commit other crimes. Sensitive data should be additionally protected by encryption during transmission and storage.
  7. Inadequate protection against attacks – many systems do not have the basic ability to detect, prevent and respond to both manual and automated attacks. You should implement mechanisms that go beyond the basic mechanisms for validating input, and include automatic detection, logging, and even blocking of attack attempts. In addition, app owners must be able to easily upload security patches.
  8. Cross-Site Request Forgery (CSRF)– consists in forcing the user's browser to send a query to the server in the context of that user. It thus allows the victim to perform some unauthorized action, e.g. changing the password, making a transfer.
  9. Using components with known vulnerabilities – components such as libraries, frameworks, and other modules used in the software operate under the same permissions as the application itself. If a vulnerable component is compromised, such an attack can pose a serious threat to the data or the system as a whole. Applications that use components with known vulnerabilities can remove the layer that protects the application by opening it to various types of attacks.
  10. Unsecured APIs – Today's applications often provide APIs for communicating with them in addition to basicfunctionality (SOAP/XML, REST/JSON, RPC, GWT, etc.). These interfaces are often insecure and contain many vulnerabilities.

Chcesz wiedzieć więcej?

Zapisz się i bądź informowany o nowych postach (zero spamu!).
Dodatkowo otrzymasz, moją prywatną listę 15 najbardziej przydatnych narzędzi (wraz z krótkim opisem), których używam przy testach penetracyjnych.

Nigdy nie podam, nie wymienię ani nie sprzedam Twojego adresu e-mail. W każdej chwili możesz zrezygnować z subskrypcji.

Bookmark the permalink.

Podziel się swoją opinią na temat artykułu