MediumGHSA-6wpv-cj6x-v3jwCVE-2015-1828

http vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

Published 13 Mar 2018 · Updated 17 Apr 2026

Is your project on an affected http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

httpRubyGems
Affected
>=0.7.0 <0.7.3
Fixed in
0.7.3
Update to the fixed version for your release line, for example:bundle update --conservative http # Gemfile: '>= 0.7.3'
httpRubyGems
Affected
<0.6.4
Fixed in
0.6.4
Update to the fixed version for your release line, for example:bundle update --conservative http # Gemfile: '>= 0.6.4'

Details

The Ruby http gem before 0.6.4 and 0.7.3 does not verify hostnames in SSL connections, which might allow remote attackers to obtain sensitive information via a man-in-the-middle-attack.

Is GHSA-6wpv-cj6x-v3jw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected http, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.