dbcve.org
Http.rbApplication · Http.rb Project

CVE-2015-1828

MEDIUM · 5.9 CVSS v3.1 Published 2017-10-06
Fix available
A fix is available. Upgrade to after 0.7.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ruby http gem before version 0.7.3 fails to perform hostname verification during SSL/TLS handshakes, meaning it accepts any valid SSL certificate regardless of whether it matches the target hostname. This allows man-in-the-middle attackers to intercept encrypted communications by presenting their own certificates.

MitigationUpgrade the Ruby http gem to version 0.7.3 or later which implements proper hostname verification for SSL connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Http.rbApplication
Affected:<= 0.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed http gem version
    Run `gem list http` or inspect your Gemfile.lock to find the version of the http gem. For Ruby code, you can also check `HTTP::VERSION` if the gem is loaded.
    Affected if The version listed is 0.7.2 or lower, or if the version cannot be determined (older gem assumed).
  2. Determine if your code makes HTTPS requests
    Search your codebase for usage of the http gem with HTTPS URLs (https://) or for calls to `HTTP.get`, `HTTP.post`, `HTTP#request` or similar methods with https:// endpoints. Also check for `use_ssl: true` options in HTTP requests.
    Affected if Your code uses the http gem to make SSL/TLS (HTTPS) connections.
  3. Check if SSL verification is explicitly disabled in your configuration
    Search for patterns like `verify_mode: OpenSSL::SSL::VERIFY_NONE`, `verify: false`, or similar SSL verification disabling options in your HTTP client initialization code.
    Affected if SSL certificate verification is explicitly disabled in your HTTP client configuration.

You are affected if the http gem version is 0.7.2 or lower AND your code uses the gem to make HTTPS connections (especially if SSL verification is disabled in the process).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.7.2
Interim mitigation

Upgrade the Ruby http gem to version 0.7.3 or later which implements proper hostname verification for SSL connections.

Fix this in Http.rb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1828 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1828 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data