shrine vulnerabilities

Shrine is a toolkit for file attachments in Ruby applications. It supports uploading, downloading, processing and deleting IO objects, backed by various storage engines. It uses efficient streaming for low memory usage. Shrine comes with a high-level interface for attaching uploaded files to database records, saving their location and metadata to a database column, and tying them to record's lifecycle. It natively supports background jobs and direct uploads for fully asynchronous user experience.

Registry
RubyGems
Latest
3.10.2
License
MIT

1 known advisory

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

Update to the latest version:bundle update --conservative shrine # Gemfile: '>= 3.10.2'

Is your project on an affected shrine?

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 shrine

  • MediumCVE-2020-15237GHSA-5jjv-x4fq-qjwp5 Oct 2020

    Possible timing attack in derivation_endpoint

    Affected
    <3.3.0
    Fixed in
    3.3.0

Is your shrine version vulnerable?

Which of your client projects still run an old shrine?

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.