Discover published sets by community

XXE attacks occur when an XML input containing a reference to an external entity is processed by a poorly configured XML parser. Risks include disclosure of confidential data, denial of service, and server-side request forgery. Prevention includes disabling external entity and DTD processing in the XML parser, and using less complex data formats such as JSON.

Security Header Injection occurs when an attacker is able to control HTTP headers added to a response by a web application. Risks include session fixation, XSS, and cache poisoning. To mitigate, validate and sanitize all headers, implement content security policy, and use httpOnly and Secure flags for cookies.

CSRF tricks a user into performing actions they didn't intend to on a web application in which they're authenticated. Risks include unauthorized changes, such as transferring funds or changing email addresses. Mitigation involves anti-CSRF tokens, SameSite cookie attributes, and using the 'double submit cookie' pattern.

RCE allows an attacker to execute arbitrary code on a server remotely. Risks include full server compromise and unauthorized system access. Mitigation strategies are to keep software up to date, use a Web Application Firewall (WAF), restrict system permissions, and regularly review code for potential vulnerabilities.

XSS allows attackers to inject client-side scripts into web pages viewed by other users. Risks involve stealing cookies, session tokens, or other sensitive information and defacing websites. Mitigations include sanitizing data input, using Content Security Policy (CSP), and secure coding practices.

Clickjacking is a technique where a user is tricked into clicking on something different from what the user perceives. Risks include executing unauthorized commands or revealing confidential information. Mitigation includes using frame busting scripts, X-Frame-Options header, and Content Security Policy (CSP).

Insecure Deserialization occurs when untrusted data is used to abuse the logic of an application, inflict a denial of service (DoS), or execute arbitrary code. Risks include remote code execution and replay attacks. Mitigation strategies are avoiding deserialization of data from untrusted sources and implementing integrity checks such as digital signatures on any serialized objects.

Sensitive Data Exposure results from insufficient protection of sensitive data, such as credit card numbers and passwords. Risks include data theft and breaches of privacy. Mitigation includes encrypting data at rest and in transit, secure tokenization, and stringent access control.

A MitM Attack occurs when a third party intercepts the communication between two systems. Risks include eavesdropping, data manipulation, and data theft. Mitigations include using HTTPS, implementing HSTS, and utilizing VPNs for secure communications.

Broken Access Control refers to restrictions on what authenticated users are allowed to do are not properly enforced. Risks include unauthorized data access and deletion or modification of data. Mitigation involves implementing a robust access control policy, using the principle of least privilege and auditing logs to detect breaches.

Security Misconfiguration happens when security settings are defined, implemented, and maintained incorrectly. Risks include unauthorized access to data or functionality and data breaches. Mitigations involve regular audits, secure installation processes, and least privilege principles.

SQL Injection is a code injection technique that might destroy your database. Risks include unauthorized viewing of data, deleting data, and full system compromise. Mitigation strategies include using prepared statements with parameterized queries, stored procedures, and input validation.

Directory Traversal, also known as path traversal, allows attackers to access restricted directories and execute commands outside of the server's root directory. Risks include unauthorized file and data access and system compromise. Mitigation includes input validation, user privileges limitations, and use of secure file access APIs.

Broken Authentication occurs when application functions related to authentication and session management are implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens. Risks include unauthorized access and impersonation. To mitigate, use multi-factor authentication, secure password storage, and rotate session ids after login.