CVE-2017-0909: private_address_check contains Incomplete List of Disallowed Inputs

CVE-2017-0909 · Severity: info · Published 2017-11-30

private_address_check contains Incomplete List of Disallowed Inputs

Technologies: private_address_check (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2017-0909 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-0909 being exploited in the wild.
How severe is CVE-2017-0909?
Informational severity, published 30 November 2017.
Which products and versions are affected?
private_address_check (RubyGems) ECOSYSTEM:introduced=0,fixed=0.4.1.
Is there a fix for CVE-2017-0909?
Yes. private_address_check (RubyGems): upgrade to 0.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-0909?
Check whether you run private_address_check (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

  • private_address_check (RubyGems): upgrade to 0.4.1 or later
    bundle update private_address_check

Affected products

  • private_address_check (RubyGems) ECOSYSTEM:introduced=0,fixed=0.4.1

Identifiers

  • CVE-2017-0909
  • GHSA-3v3c-r5v2-68ph

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