OWASP Flashcards
owasp 1: injection flaws
- SQL ldap trick interpreter into executing attackers unintended commands or accessing data
owasp 2: Broken Authentication and session Management
App functions related to Auth and Session management not implemented correctly allows attacker to compromise passwords keys or session tokens or other to assume users identities. Password spraying, phishing, mit
Simply stated, broken authentication & session management allows a cybercriminal to steal a user’s login data, or forge session data, such as cookies
owasp 3: Sensitive Data exposure
Inadequately protected data ie pii. Should be encrypted in transit Attacker steal and use.
owasp 4: XML External Entities
(XXE) Attacker exploit vulnerable xml processors if they can include hostile content in XML exploiting code, dependencies or integrations. Older XML processors allow specification to an external entity, a URI that is dereferenced and evaluated during processing. This can be used to extract data, execute remote script, scan an internal system, perform dos, and other allows an attacker to interfere with an application’s processing of XML data
owasp 5: 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. IDOR GET vs PUT, directory traversal, getting an admin page. Client side caching.
owasp 6: 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.
owasp 7: Cross Site Scripting
(XSS) XSS allows attackers to execute scripts in the victims browser that can hijack user sessions, deface websites, or redirect to malicious sites.
owasp 8: 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.
goes from string back to binary
owasp 9: 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. with known vulnerabilities
not implemented correctly allows attacker to compromise passwords keys or session tokens or other to assume users identities. Password spraying, phishing, mitm
owasp 2: Broken Authentication and session Management
Attacker exploit vulnerable xml processors if they can include hostile content in XML exploiting code, dependencies or integrations. Older XML processors allow specification to an external entity, a URI that is dereferenced and evaluated during processing. This can be used to extract data, execute remote script, scan an internal system, perform dos, and other allows an attacker to interfere with an application’s processing of XML data
owasp 4: XML External Entities
trick interpreter into executing attackers unintended commands or accessing data
owasp 1: injection flaws
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.
owasp 9: Using components with known vulnerabilities
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.
owasp 6: Security Misconfiguration
leads to remote code execution. Even if no remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.
goes from string back to binary
owasp 8: Insecure Deserialization
