Skip to content

← Public intelligence

RubyGems package

json-jwt

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedRubyGemsPublished

    json-jwt allows bypass of identity checks via a sign/encryption confusion attack

    CVE-2023-51774 · GHSA-c8v6-786g-vjx6

    Affected
    • RubyGems json-jwt >= 1.16.0, < 1.16.6; < 1.15.3.1
    Fixed in
    1.16.61.15.3.1· Vendor fix available
    Issue
    The json-jwt (aka JSON::JWT) gem 1.16.x before 1.16.6, 1.15.x before 1.15.3.1 for Ruby sometimes allows bypass of identity checks via a sign/encryption confusion attack. For example, JWE can sometimes be used to bypass JSON::JWT.decode.

    Recommended action: Upgrade to 1.16.6 or 1.15.3.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5RubyGemsPublished

    JSON-jwt Gem lacked element count during splitting of JWE string

    CVE-2019-18848 · GHSA-cff7-6h4q-q5pj

    Affected
    • RubyGems json-jwt < 1.11.0
    Fixed in
    1.11.0· Vendor fix available
    Issue
    The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string.

    Recommended action: Upgrade to 1.11.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 5.3RubyGemsPublished

    Json-jwt did not verify the cryptographic signature for data

    CVE-2018-1000539 · GHSA-mj4x-wcxf-hm8x

    Affected
    • RubyGems json-jwt >= 0.5.1, < 1.9.4
    Fixed in
    1.9.4· Vendor fix available
    Issue
    The json-jwt rubygem 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.

    Recommended action: Upgrade to 1.9.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →