HighGHSA-7359-3c6r-hfc2CVE-2016-11086

Improper Certificate Validation in oauth ruby gem

Published 22 Apr 2021 · Updated 8 Nov 2023

Is your project on an affected oauth?

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 package

oauthRubyGems
Affected
<0.5.5
Fixed in
0.5.5
Update to the fixed version for your release line, for example:bundle update --conservative oauth # Gemfile: '>= 0.5.5'

Details

lib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information.

Is GHSA-7359-3c6r-hfc2 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 oauth, and gives you the command that fixes it.

More advisories for oauth

  • HighCVE-2026-54605OAuth: Cross-origin token-request redirects can expose signed request metadata · 28 Jul 2026
oauth security overview

References

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