Timing attack in Shrine
Priority LOW 28CWE-203Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-203.
Summary
In Shrine before version 3.3.0, when using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL. The problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater. A possible workaround is provided in the linked advisory.
Why it matters now
EPSS 0.01015 63rd percentileScored 2026-11-07
Fix Fixed shrine (shrinerb): 3.3.0shrine (RubyGems): 3.3.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| shrinerb | shrine | before 3.3.0 | 3.3.0 | Patch available | CNA |
| — | shrine (RubyGems) | before 3.3.0 | 3.3.0 | Patch available | GHSA-5jjv-x4fq-qjwp |
- shrine Vendorshrinerb Affected before 3.3.0 Fixed in 3.3.0 Patch available CNA
- shrine (RubyGems) Vendor— Affected before 3.3.0 Fixed in 3.3.0 Patch available GHSA-5jjv-x4fq-qjwp
Remediation
- Fix · CNA shrine (shrinerb) Fixed in 3.3.0
- Fix · GHSA-5jjv-x4fq-qjwp shrine (RubyGems) Fixed in 3.3.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2020-15237
- 2026-10-03 Alias added: GHSA-5jjv-x4fq-qjwp
References
Advisory 2
Sources
- CVE-2020-15237 · CVE Program
- CVE-2020-15237 · NVD
- FIRST EPSS
- GHSA-5jjv-x4fq-qjwp · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences