نسخههای متأثر
Ubuntu24.04:LTS/ruby-jwt
- نسخههای متأثر
- <2.7.1-1+deb13u1build0.24.04.1
- نسخهٔ اصلاحشده
- 2.7.1-1+deb13u1build0.24.04.1
Ubuntu26.04:LTS/ruby-jwt
- نسخههای متأثر
- <2.7.1-1+deb13u1build0.26.04.1
- نسخهٔ اصلاحشده
- 2.7.1-1+deb13u1build0.26.04.1
UbuntuPro:16.04:LTS/ruby-jwt
- نسخههای متأثر
- <1.0.0-3ubuntu0.1~esm1
- نسخهٔ اصلاحشده
- 1.0.0-3ubuntu0.1~esm1
UbuntuPro:18.04:LTS/ruby-jwt
- نسخههای متأثر
- <1.5.6-1ubuntu0.1~esm1
- نسخهٔ اصلاحشده
- 1.5.6-1ubuntu0.1~esm1
UbuntuPro:20.04:LTS/ruby-jwt
- نسخههای متأثر
- <2.1.0-2ubuntu0.1~esm1
- نسخهٔ اصلاحشده
- 2.1.0-2ubuntu0.1~esm1
UbuntuPro:22.04:LTS/ruby-jwt
- نسخههای متأثر
- <2.2.2-1ubuntu0.1~esm1
- نسخهٔ اصلاحشده
- 2.2.2-1ubuntu0.1~esm1
شرح آسیبپذیری
ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0.
پیوندها
- https://github.com/jwt/ruby-jwt/commit/9820020869ad147b941e49d96ab8beba35532964
- https://github.com/jwt/ruby-jwt/commit/db560b769a07bd9724e77ff505011ac01872106f
- https://github.com/jwt/ruby-jwt/releases/tag/v2.10.3
- https://github.com/jwt/ruby-jwt/releases/tag/v3.2.0
- https://github.com/jwt/ruby-jwt/security/advisories/GHSA-c32j-vqhx-rx3x
- https://ubuntu.com/security/CVE-2026-45363
- https://ubuntu.com/security/notices/USN-9059-1
- https://www.cve.org/CVERecord?id=CVE-2026-45363

