Skip to content
Sign in
CVE-2020-152375.9MediumCWE-208

CVE-2020-15237: Timing attack in Shrine

shrinerb · shrine

Affected: shrinerb · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.0%probability of exploitation in the next 30 days
63rd percentile
050100

Higher than 63% of scored CVEs

5.9MediumCVSS 3.1
LowMedium

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • shrinerb · shrine< 3.3.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-15237 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in