CVE-2024-32970

{"id": "CVE-2024-32970", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.2, "exploitabilityScore": 2.8}]}, "published": "2024-04-30T23:15:06.483", "references": [{"url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy", "source": "security-advisories@github.com"}, {"url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#unsafe-inline", "source": "security-advisories@github.com"}, {"url": "https://github.com/payloadbox/xss-payload-list", "source": "security-advisories@github.com"}, {"url": "https://github.com/phlex-ruby/phlex/commit/da8f94342a84cff9d78c98bcc3b3604ee2e577d2", "source": "security-advisories@github.com"}, {"url": "https://github.com/phlex-ruby/phlex/security/advisories/GHSA-9p57-h987-4vgx", "source": "security-advisories@github.com"}, {"url": "https://rubygems.org/gems/phlex", "source": "security-advisories@github.com"}, {"url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#unsafe-inline", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/payloadbox/xss-payload-list", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/phlex-ruby/phlex/commit/da8f94342a84cff9d78c98bcc3b3604ee2e577d2", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/phlex-ruby/phlex/security/advisories/GHSA-9p57-h987-4vgx", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://rubygems.org/gems/phlex", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-79"}]}], "descriptions": [{"lang": "en", "value": "Phlex is a framework for building object-oriented views in Ruby. In affected versions there is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. Since the last two vulnerabilities https://github.com/phlex-ruby/phlex/security/advisories/GHSA-242p-4v39-2v8g and https://github.com/phlex-ruby/phlex/security/advisories/GHSA-g7xq-xv8c-h98c, we have invested in extensive browser tests. It was these new tests that helped us uncover these issues. As of now the project exercises every possible attack vector the developers can think of \u2014 including enumerating every ASCII character, and we run these tests in Chrome, Firefox and Safari. Additionally, we test against a list of 6613 known XSS payloads (see: payloadbox/xss-payload-list). The reason these issues were not detected before is the escapes were working as designed. However, their design didn't take into account just how recklessly permissive browsers are when it comes to executing unsafe JavaScript via HTML attributes. If you render an `<a>` tag with an `href` attribute set to a user-provided link, that link could potentially execute JavaScript when clicked by another user. If you splat user-provided attributes when rendering any HTML or SVG tag, malicious event attributes could be included in the output, executing JavaScript when the events are triggered by another user. Patches are available on RubyGems for all minor versions released in the last year. Users are advised to upgrade. Users unable to upgrade should configure a Content Security Policy that does not allow `unsafe-inline` which would effectively prevent this vulnerability from being exploited. Users who upgrade are also advised to configure a Content Security Policy header that does not allow `unsafe-inline`."}, {"lang": "es", "value": "Phlex es un framework para crear vistas orientadas a objetos en Ruby. En las versiones afectadas existe una posible vulnerabilidad de Cross Site Scripting (XSS) que puede explotarse a trav\u00e9s de datos de usuario creados con fines malintencionados. Desde las dos \u00faltimas vulnerabilidades https://github.com/phlex-ruby/phlex/security/advisories/GHSA-242p-4v39-2v8g y https://github.com/phlex-ruby/phlex/security/advisories/GHSA -g7xq-xv8c-h98c, hemos invertido en pruebas exhaustivas del navegador. Fueron estas nuevas pruebas las que nos ayudaron a descubrir estos problemas. A partir de ahora, el proyecto practica todos los posibles vectores de ataque que los desarrolladores puedan imaginar, incluida la enumeraci\u00f3n de cada car\u00e1cter ASCII, y ejecutamos estas pruebas en Chrome, Firefox y Safari. Adem\u00e1s, realizamos pruebas con una lista de 6613 cargas \u00fatiles XSS conocidas (consulte: payloadbox/xss-payload-list). La raz\u00f3n por la que estos problemas no se detectaron antes es que los escapes funcionaban seg\u00fan lo manipulado. Sin embargo, su dise\u00f1o no tuvo en cuenta cu\u00e1n imprudentemente permisivos son los navegadores cuando se trata de ejecutar JavaScript inseguro a trav\u00e9s de atributos HTML. Si representa una etiqueta `<a rel=\"nofollow\">` con un atributo `href` establecido en un enlace proporcionado por el usuario, ese enlace podr\u00eda ejecutar JavaScript cuando otro usuario haga clic en \u00e9l. Si agrega atributos proporcionados por el usuario al representar cualquier etiqueta HTML o SVG, se podr\u00edan incluir atributos de eventos maliciosos en la salida, ejecutando JavaScript cuando los eventos sean activados por otro usuario. Los parches est\u00e1n disponibles en RubyGems para todas las versiones menores lanzadas el a\u00f1o pasado. Se recomienda a los usuarios que actualicen. Los usuarios que no puedan actualizar deben configurar una Pol\u00edtica de seguridad de contenido que no permita \"inseguro en l\u00ednea\", lo que evitar\u00eda efectivamente que se aproveche esta vulnerabilidad. Tambi\u00e9n se recomienda a los usuarios que actualicen que configuren un encabezado de Pol\u00edtica de seguridad de contenido que no permita \"inseguro en l\u00ednea\".</a>"}], "lastModified": "2024-11-21T09:16:08.173", "sourceIdentifier": "security-advisories@github.com"}