CVE-2020-15237 json
Timing attack in Shrine
published 2020-10-05 6 y ago modified 2026-07-08 4 mo ago also GHSA-5jjv-x4fq-qjwp , EUVD-2020-1413
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
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.
Patch / fix
Exploit prediction
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | shrine | <3.3.0 |
3.3.0 |
Affected products
- shrinerb shrine
Classification
References
-
github.com
/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0
web, patch, third-party-advisory
-
github.com
/shrinerb/shrine/security/advisories/GHSA-5jjv-x4fq-qjwp
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15237
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/shrine/CVE-2020-15237.yml
web
-
github.com
/shrinerb/shrine
package
Sources
- CVE List CVE-2020-15237
- GitHub Advisory GHSA-5jjv-x4fq-qjwp
- NVD CVE-2020-15237
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.