VDB

CVE-2018-1000539

CVE-2018-1000539 PUBLISHED

Json-jwt did not verify the cryptographic signature for data

Reported by mitre · Published June 26, 2018

json-jwt is fixed in 1.9.4 (RubyGems)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
json-jwtRubyGems1.9.4

Affected products

VendorProductVersions
n/an/an/a
n/an/a*

Timeline

  • Jun 26, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 5, 2024 CVE Updated
  • Mar 17, 2026 Security Advisory (2 in total, the first dated here)
  • Sep 26, 2026 Coalition ESS Score
  • Oct 31, 2026 Distribution Patch

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-1000539
vulnetix vdb fixes CVE-2018-1000539

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-1000539/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_MISC
  • DSA-4283 vendor-advisoryx_refsource_DEBIAN
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›