CVE-2015-1828 json
http vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
published 2017-10-06 9 y ago modified 2026-06-17 4 mo ago also GHSA-6wpv-cj6x-v3jw , EUVD-2018-0172
- cvss
- 5.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
The Ruby http gem before 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.
Patch / fix
- rubygems http 0.6.4, 0.7.3
- ruby-http Debian 14, Debian 13, Debian 12 1.0.2-2
debian advisories DEBIAN-CVE-2015-1828
Exploit prediction
1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | http | >=0.7.0, <0.7.3 <0.6.4 |
0.7.3 0.6.4 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
rubysec.com
/advisories/http-CVE-2015-1828
web, third-party-advisory
-
github.com
/ruby/openssl/issues/8
web, issue-tracking, third-party-advisory
- groups.google.com /forum/#%21topic/httprb/jkb4oxwZjkU
-
nvd.nist.gov
/vuln/detail/CVE-2015-1828
advisory
-
github.com
/httprb/http
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/http/CVE-2015-1828.yml
web
-
groups.google.com
/forum/#!topic/httprb/jkb4oxwZjkU
web
-
my.diffend.io
/gems/http/0.6.3/0.6.4
web
-
my.diffend.io
/gems/http/0.7.2/0.7.3
web
Sources
- CVE List CVE-2015-1828
- GitHub Advisory GHSA-6wpv-cj6x-v3jw
- NVD CVE-2015-1828
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.