# CVE-2016-7798: OpenSSL gem for Ruby using inadequate encryption strength

Source: https://junglewise.ai/threats/cve-2016-7798-openssl-gem-for-ruby-using-inadequate-encryption-strength  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2017-10-24  
License: CC BY 4.0 with a link back

CVE-2016-7798 · Severity: low · CVSS 3.1 · Published 2017-10-24

OpenSSL gem for Ruby using inadequate encryption strength

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

## Quick answers

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

**How severe is CVE-2016-7798?** Low severity, with a CVSS score of 3.1, published 24 October 2017.

**Which products and versions are affected?** openssl (RubyGems) ECOSYSTEM:introduced=0,fixed=2.0.0.

**Is there a fix for CVE-2016-7798?** Yes. openssl (RubyGems): upgrade to 2.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2016-7798?** Check whether you run openssl (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

- openssl (RubyGems): upgrade to 2.0.0 or later

  ```sh
  bundle update openssl
  ```


## Affected products

- openssl (RubyGems) ECOSYSTEM:introduced=0,fixed=2.0.0

## Identifiers

- CVE-2016-7798
- GHSA-6h88-qjpv-p32m

## Related threats

- [Ruby OpenSSL DoS Vulnerability](https://junglewise.ai/threats/cve-2017-14033-ruby-openssl-dos-vulnerability)
- [Ruby Openssl Allows Incorrect Value Comparison](https://junglewise.ai/threats/cve-2018-16395-ruby-openssl-allows-incorrect-value-comparison)