CVE-2018-1000539: Json-jwt did not verify the cryptographic signature for data

CVE-2018-1000539 · Severity: low · CVSS 3 · Published 2018-07-31

Json-jwt did not verify the cryptographic signature for data

Technologies: json-jwt (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2018-1000539 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000539 being exploited in the wild.
How severe is CVE-2018-1000539?
Low severity, with a CVSS score of 3, published 31 July 2018.
Which products and versions are affected?
json-jwt (RubyGems) ECOSYSTEM:introduced=0.5.1,fixed=1.9.4.
Is there a fix for CVE-2018-1000539?
Yes. json-jwt (RubyGems): upgrade to 1.9.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000539?
Check whether you run json-jwt (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • json-jwt (RubyGems): upgrade to 1.9.4 or later
    bundle update json-jwt

Affected products

  • json-jwt (RubyGems) ECOSYSTEM:introduced=0.5.1,fixed=1.9.4

Identifiers

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.