shrine

Version	Released
`3.10.2` patch	Oct 11, 2026
`3.10.1` patch	Oct 10, 2026
`3.10.0` minor	Sep 20, 2026
`3.9.0` minor	Jul 13, 2026
`3.8.0` minor	Jun 24, 2026
`3.7.1` patch	Jun 03, 2026
`3.7.0` minor	May 27, 2026
`3.6.0` minor	Apr 29, 2024
`3.5.0` minor	Jul 07, 2023
`3.4.0` minor	Jun 14, 2021
`3.3.0` minor	Oct 04, 2020
`3.2.2` patch 1 CVE	Aug 05, 2020
`2.19.4` patch 1 CVE	Jan 16, 2020
`3.2.1` patch 1 CVE	Jan 15, 2020
`3.2.0` minor 1 CVE	Dec 17, 2019
`3.1.0` minor 1 CVE	Nov 15, 2019
`3.0.1` patch 1 CVE	Oct 17, 2019
`3.0.0` major 1 CVE	Oct 14, 2019
`3.0.0.rc` pre 1 CVE	Sep 28, 2019
`3.0.0.beta3` pre 1 CVE	Sep 25, 2019
`3.0.0.beta2` pre 1 CVE	Sep 11, 2019
`3.0.0.beta` pre 1 CVE	Aug 29, 2019
`3.0.0.alpha` pre 1 CVE	Aug 19, 2019
`2.19.3` patch 1 CVE	Aug 09, 2019
`2.19.2` patch 1 CVE	Jul 25, 2019
`2.19.1` patch 1 CVE	Jul 20, 2019
`2.19.0` minor 1 CVE	Jul 18, 2019
`2.18.1` patch 1 CVE	Jul 05, 2019
`2.18.0` minor 1 CVE	Jun 24, 2019
`2.17.1` patch 1 CVE	May 15, 2019
`2.17.0` minor 1 CVE	May 08, 2019
`2.16.0` minor 1 CVE	Feb 18, 2019
`2.15.0` minor 1 CVE	Feb 08, 2019
`2.14.0` minor 1 CVE	Dec 27, 2018
`2.13.0` minor 1 CVE	Nov 04, 2018
`2.12.0` minor 1 CVE	Aug 21, 2018
`2.11.0` minor 1 CVE	Apr 28, 2018
`2.10.1` patch 1 CVE	Apr 02, 2018
`2.10.0` minor 1 CVE	Mar 28, 2018
`2.9.0` minor 1 CVE	Jan 27, 2018
`2.8.0` minor 1 CVE	Oct 11, 2017
`2.7.0` minor 1 CVE	Sep 11, 2017
`2.6.1` patch 1 CVE	Apr 12, 2017
`2.6.0` minor 1 CVE	Apr 04, 2017
`2.5.0` minor 1 CVE	Nov 11, 2016
`2.4.1` patch 1 CVE	Oct 17, 2016
`2.4.0` minor 1 CVE	Oct 10, 2016
`2.3.1` patch 1 CVE	Sep 01, 2016
`2.3.0` minor 1 CVE	Aug 27, 2016
`2.2.0` minor 1 CVE	Jul 29, 2016

3.10.2 patch

Oct 11, 2026

3.10.1 patch

Oct 10, 2026

3.10.0 minor

Sep 20, 2026

3.9.0 minor

Jul 13, 2026

3.8.0 minor

Jun 24, 2026

3.7.1 patch

Jun 03, 2026

3.7.0 minor

May 27, 2026

3.6.0 minor

Apr 29, 2024

3.5.0 minor

Jul 07, 2023

3.4.0 minor

Jun 14, 2021

3.3.0 minor

Oct 04, 2020

3.2.2 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 05, 2020

2.19.4 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 16, 2020

3.2.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 15, 2020

3.2.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Dec 17, 2019

3.1.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 15, 2019

3.0.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 17, 2019

3.0.0 major

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 14, 2019

3.0.0.rc pre

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 28, 2019

3.0.0.beta3 pre

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 25, 2019

3.0.0.beta2 pre

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 11, 2019

3.0.0.beta pre

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 29, 2019

3.0.0.alpha pre

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 19, 2019

2.19.3 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 09, 2019

2.19.2 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 25, 2019

2.19.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 20, 2019

2.19.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 18, 2019

2.18.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 05, 2019

2.18.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jun 24, 2019

2.17.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

May 15, 2019

2.17.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

May 08, 2019

2.16.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Feb 18, 2019

2.15.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Feb 08, 2019

2.14.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Dec 27, 2018

2.13.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 04, 2018

2.12.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 21, 2018

2.11.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Apr 28, 2018

2.10.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Apr 02, 2018

2.10.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Mar 28, 2018

2.9.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jan 27, 2018

2.8.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 11, 2017

2.7.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 11, 2017

2.6.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Apr 12, 2017

2.6.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Apr 04, 2017

2.5.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 11, 2016

2.4.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 17, 2016

2.4.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Oct 10, 2016

2.3.1 patch

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Sep 01, 2016

2.3.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Aug 27, 2016

2.2.0 minor

1 CVE

CVE-2020-15237 GHSA-5jjv-x4fq-qjwp Oct 05, 2020

Possible timing attack in derivation_endpoint

5.9 / 10

Medium

Network High None None Unchanged High None None

Impact

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.

Patches

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.

Workarounds

Users of older Shrine versions can apply the following monkey-patch after loading the derivation_endpoint plugin:

class Shrine
  class UrlSigner
    def verify_signature(string, signature)
      if signature.nil?
        fail InvalidSignature, "missing \"signature\" param"
      elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
        fail InvalidSignature, "provided signature does not match the calculated signature"
      end
    end
  end
end

References

You can read more about timing attacks here.

Affected versions


          0.9.0


          1.0.0


          1.1.0


          1.2.0


          1.3.0


          1.4.0


          1.4.1


          1.4.2


          2.0.0


          2.0.1


          2.1.0


          2.1.1

+ 39 more


            2.10.0


            2.10.1


            2.11.0


            2.12.0


            2.13.0


            2.14.0


            2.15.0


            2.16.0


            2.17.0


            2.17.1


            2.18.0


            2.18.1


            2.19.0


            2.19.1


            2.19.2


            2.19.3


            2.19.4


            2.2.0


            2.3.0


            2.3.1


            2.4.0


            2.4.1


            2.5.0


            2.6.0


            2.6.1


            2.7.0


            2.8.0


            2.9.0


            3.0.0


            3.0.0.alpha


            3.0.0.beta


            3.0.0.beta2


            3.0.0.beta3


            3.0.0.rc


            3.0.1


            3.1.0


            3.2.0


            3.2.1


            3.2.2

Fixed in


          3.3.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Jul 29, 2016

Activity

Reach

Details