recurly vulnerabilities

The ruby client for Recurly's V3 API

Registry
RubyGems
Latest
4.86.0
License
MIT

1 known advisory

The latest version, 4.86.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:bundle update --conservative recurly # Gemfile: '>= 4.86.0'

Is your project on an affected recurly?

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

Security advisories for recurly

  • CriticalCVE-2017-0905GHSA-x27v-x225-gq8g6 Dec 2017

    Recurly gem Server-Side Request Forgery in Resource#find method

    Affected
    >=2.3.0 <2.3.10 · >=2.2.0 <2.2.5 · >=2.1.0 <2.1.11 · >=2.0.0 <2.0.13 · >=2.9.0 <2.9.2 · >=2.8.0 <2.8.2 · >=2.7.0 <2.7.8 · >=2.6.0 <2.6.3 · >=2.5.0 <2.5.4 · >=2.4.0 <2.4.11 · >=2.11.0 <2.11.3 · >=2.10.0 <2.10.4
    Fixed in
    2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3

Is your recurly version vulnerable?

Which of your client projects still run an old recurly?

NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other RubyGems packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.