Page 2 of 11 results (0.004 seconds)

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

The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string. La gema json-jwt versiones anteriores a 1.11.0 para Ruby, carece de un conteo de elementos durante la división de una cadena JWE. • https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a https://github.com/nov/json-jwt/compare/v1.10.2...v1.11.0 https://lists.debian.org/debian-lts-announce/2020/10/msg00001.html • CWE-287: Improper Authentication •

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

perl-CRYPT-JWT 0.022 and earlier is affected by: Incorrect Access Control. The impact is: bypass authentication. The component is: JWT.pm for JWT security token, line 614 in _decode_jws(). The attack vector is: network connectivity(crafting user-controlled input to bypass authentication). The fixed version is: 0.023. perl-CRYPT-JWT versión 0.022 y versiones anteriores esta afectado por: Control de Acceso Incorrecto. • https://github.com/DCIT/perl-Crypt-JWT/issues/3#issuecomment-417947483 • CWE-347: Improper Verification of Cryptographic Signature •

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

Nov json-jwt version >= 0.5.0 && < 1.9.4 contains a CWE-347: Improper Verification of Cryptographic Signature vulnerability in Decryption of AES-GCM encrypted JSON Web Tokens that can result in Attacker can forge a authentication tag. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 1.9.4 and later. Nov json-jwt, en versiones 0.5.0 hasta la 1.9.4 contiene una vulnerabilidad CWE-347: verificación incorrecta de firmas criptográficas en el descifrado de tokens web JSON cifrados por AES-GCM que puede resultar en que un atacante falsifique una etiqueta de autenticación. Este ataque parece ser explotable mediante conectividad de red. • https://github.com/nov/json-jwt/pull/62 https://www.debian.org/security/2018/dsa-4283 • CWE-347: Improper Verification of Cryptographic Signature •

CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 2

Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants. Como "algorithm" no se aplica en jwt.decode() en jwt-simple en versiones 0.3.0 y anteriores, un usuario malicioso podría elegir qué algoritmo se envía al servidor. Si el servidor espera RSA pero recibe HMAC-SHA con la clave pública RSA, el servidor pensará que la clave pública es, en realidad, una clave privada HMAC. • https://github.com/thepcn3rd/jwtToken-CVE-2016-10555 https://github.com/scent2d/PoC-CVE-2016-10555 https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries https://github.com/hokaccha/node-jwt-simple/pull/14 https://github.com/hokaccha/node-jwt-simple/pull/16 https://nodesecurity.io/advisories/87 • CWE-20: Improper Input Validation CWE-310: Cryptographic Issues •

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

A time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests. Una comprobación de igualdad sensible al tiempo en la firma JWT en el método JsonWebToken.validate en main/scala/authentikat/jwt/JsonWebToken.scala en authentikat-jwt (también conocido como com.jason-goodwin/authentikat-jwt), en versiones 0.4.5 y anteriores, permite que el proveedor de un token JWT adivine bit tras bit de la firma mediante la repetición de peticiones de validación. • https://github.com/jasongoodwin/authentikat-jwt/commit/2d2fa0d40ac8f2f7aa7e9b070fa1a25eee082cb0 https://github.com/jasongoodwin/authentikat-jwt/issues/12 https://github.com/jasongoodwin/authentikat-jwt/pull/36 •