# CVE-2019-18848: JSON-jwt Gem lacked element count during splitting of JWE string

Source: https://junglewise.ai/threats/cve-2019-18848-json-jwt-gem-lacked-element-count-during-splitting-of-jwe-string  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-11-14  
License: CC BY 4.0 with a link back

CVE-2019-18848 · Severity: low · CVSS 3.1 · Published 2019-11-14

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

Technologies: [json-jwt (RubyGems)](https://junglewise.ai/threats/technologies/json-jwt). Vendors: [RubyGems](https://junglewise.ai/threats/vendors/rubygems).

## Quick answers

**Is CVE-2019-18848 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2019-18848 being exploited in the wild.

**How severe is CVE-2019-18848?** Low severity, with a CVSS score of 3.1, published 14 November 2019.

**Which products and versions are affected?** json-jwt (RubyGems) ECOSYSTEM:introduced=0,fixed=1.11.0.

**Is there a fix for CVE-2019-18848?** Yes. json-jwt (RubyGems): upgrade to 1.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2019-18848?** 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.11.0 or later

  ```sh
  bundle update json-jwt
  ```


## Affected products

- json-jwt (RubyGems) ECOSYSTEM:introduced=0,fixed=1.11.0

## Identifiers

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

## Related threats

- [json-jwt allows bypass of identity checks via a sign/encryption confusion attack](https://junglewise.ai/threats/cve-2023-51774-json-jwt-allows-bypass-of-identity-checks-via-a-sign-encryption)
- [Json-jwt did not verify the cryptographic signature for data](https://junglewise.ai/threats/cve-2018-1000539-json-jwt-did-not-verify-the-cryptographic-signature-for-data)