CVSS: 9.2EPSS: 0%CPEs: 1EXPL: 1CVE-2023-25581 – Deserialization of untrusted data in InternalAttributeHandler in pac4j
https://notcve.org/view.php?id=CVE-2023-25581
pac4j is a security framework for Java. `pac4j-core` prior to version 4.0.0 is affected by a Java deserialization vulnerability. The vulnerability affects systems that store externally controlled values in attributes of the `UserProfile` class from pac4j-core. It can be exploited by providing an attribute that contains a serialized Java object with a special prefix `{#sb64}` and Base64 encoding. This issue may lead to Remote Code Execution (RCE) in the worst case. • https://github.com/p33d/CVE-2023-25581 https://github.com/frohoff/ysoserial https://github.com/pac4j/pac4j/blob/5834aeb22ad3a4369dfa572be60d7b20f5784a8f/pac4j-core/src/main/java/org/pac4j/core/profile/InternalAttributeHandler.java#L95 https://portswigger.net/web-security/deserialization https://securitylab.github.com/advisories/GHSL-2022-085_pac4j • CWE-502: Deserialization of Untrusted Data •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2021-44878
https://notcve.org/view.php?id=CVE-2021-44878
If an OpenID Connect provider supports the "none" algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the "idtoken" response type which is not secure and violates the OpenID Core Specification. The "none" algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using "none" as the value of "alg" key in the header with an empty signature value. Si un proveedor de OpenID Connect soporta el algoritmo "none" (es decir, tokens sin firma), pac4j v5.3.0 (y anteriores) no lo rechaza sin una configuración explícita por su parte o para el tipo de respuesta "idtoken", que no es seguro y viola la especificación OpenID Core. El algoritmo "none" no requiere ninguna verificación de firma al validar los tokens de identificación, lo que permite al atacante saltarse la validación de tokens inyectando un token de identificación malformado utilizando "none" como valor de la clave "alg" en la cabecera con un valor de firma vacío • https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae https://openid.net/specs/openid-connect-core-1_0.html#IDToken https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html • CWE-347: Improper Verification of Cryptographic Signature •
CVSS: 4.9EPSS: 0%CPEs: 1EXPL: 0CVE-2019-10755
https://notcve.org/view.php?id=CVE-2019-10755
The SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomStringUtils class which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong. This issue only affects the 3.X release of pac4j-saml. Se encontró que el identificador SAML generado dentro del archivo SAML2Utils.java utiliza la clase RacheStringUtils de apache commons-lang3 que los hace predecibles debido a que el algoritmo de RandomStringUtils PRNG no es criptográficamente fuerte. Este problema solo afecta a las versiones 3.X publicación de pac4j-saml. • https://snyk.io/vuln/SNYK-JAVA-ORGPAC4J-467407 • CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) •