Page 2 of 32 results (0.003 seconds)

CVSS: 10.0EPSS: 0%CPEs: 6EXPL: 0

20 Sep 2022 — The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart requests by submitting a payload that uses a character encoding scheme via the Content-Type or the deprecated Content-Transfer-Encoding multipart MIME header fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The le... • https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves • CWE-116: Improper Encoding or Escaping of Output CWE-863: Incorrect Authorization •

CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0

20 Sep 2022 — The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an HTTP Accept header field containing an optional "charset" parameter in order to receive the response in an encoded form. Depending on the "charset", this response can not be decoded by the web application firewall. A restricted resource, access to which would ordinarily be detected, may therefore bypass detection. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported vers... • https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves • CWE-116: Improper Encoding or Escaping of Output CWE-693: Protection Mechanism Failure •

CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0

20 Sep 2022 — The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small byte range. A restricted resource, access to which would ordinarily be detected, may be exfiltrated from the backend, despite being protected by a web application firewall that uses CRS. Short subsections of a restricted resource may bypass pattern matching techniques and allow undetected access. Th... • https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves • CWE-116: Improper Encoding or Escaping of Output CWE-863: Incorrect Authorization •

CVSS: 10.0EPSS: 0%CPEs: 2EXPL: 2

02 Sep 2022 — Modsecurity owasp-modsecurity-crs 3.2.0 (Paranoia level at PL1) has a SQL injection bypass vulnerability. Attackers can use the comment characters and variable assignments in the SQL syntax to bypass Modsecurity WAF protection and implement SQL injection attacks on Web applications. Modsecurity owasp-modsecurity-crs versión 3.2.0 (nivel de paranoia en PL1) presenta una vulnerabilidad de omisión de inyección SQL. Los atacantes pueden usar los caracteres de comentario y las asignaciones de variables en la sin... • https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1727 • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •

CVSS: 6.1EPSS: 0%CPEs: 8EXPL: 1

27 Apr 2022 — ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, there is a potential for a cross-site scripting vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the **antisamy-esapi.xml** configuration file that can cause "javascript:" URLs to fail to be correctly sanitized. This issue is patched in ESAPI 2.3.0.0. As a workaround, manually edit the **antisamy-esapi.xml** configuration files to change the ... • https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/ESAPI-security-bulletin8.pdf • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 9.8EPSS: 0%CPEs: 8EXPL: 1

25 Apr 2022 — ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0... • https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.3.0.0-release-notes.txt • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0

24 Mar 2022 — OWASP Zed Attack Proxy (ZAP) through w2022-03-21 does not verify the TLS certificate chain of an HTTPS server. OWASP Zed Attack Proxy (ZAP) versiones hasta w2022-03-21, no verifica la cadena de certificados TLS de un servidor HTTPS • http://www.openwall.com/lists/oss-security/2022/03/24/3 • CWE-295: Improper Certificate Validation •

CVSS: 9.8EPSS: 0%CPEs: 6EXPL: 3

05 Nov 2021 — OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected by a Request Body Bypass via a trailing pathname. OWASP ModSecurity Core Rule Set versiones 3.1.x anteriores a 3.1.2, 3.2.x anteriores a 3.2.1 y 3.3.x anteriores a 3.3.2, está afectado por un desvío del cuerpo de la petición por medio de un nombre de ruta final Multiple vulnerabilities have been discovered in ModSecurity Core Rule Set, the worst of which could result in bypassing the WAF. Versions grea... • https://coreruleset.org/20210630/cve-2021-35368-crs-request-body-bypass •

CVSS: 9.8EPSS: 0%CPEs: 8EXPL: 1

18 Oct 2021 — The OWASP Java HTML Sanitizer before 20211018.1 does not properly enforce policies associated with the SELECT, STYLE, and OPTION elements. OWASP Java HTML Sanitizer versiones anteriores a 20211018.1, no aplica apropiadamente las políticas asociadas a los elementos SELECT, STYLE y OPTION • https://docs.google.com/document/d/11SoX296sMS0XoQiQbpxc5pNxSdbJKDJkm5BDv0zrX50 • CWE-20: Improper Input Validation •

CVSS: 8.8EPSS: 0%CPEs: 2EXPL: 0

19 Aug 2021 — In OWASP CSRFGuard through 3.1.0, CSRF can occur because the CSRF cookie may be retrieved by using only a session token. En OWASP CSRFGuard versiones hasta 3.1.0, un ataque de tipo CSRF puede ocurrir porque la cookie CSRF puede ser recuperada usando sólo un token de sesión. • https://github.com/reidmefirst/vuln-disclosure/blob/main/2021-01.txt • CWE-352: Cross-Site Request Forgery (CSRF) •