{"answers":{"affected":"2 open source packages ship an affected version, including shrine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15237 in the wild and no public exploit code.","fix":"Upgrade shrine to 3.3.0 or later.","what":"CVE-2020-15237 is a medium-severity vulnerability in shrinerb shrine, published on 5 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15237 and fix it if it is affected.\n\nWhat it is: CVE-2020-15237 is a medium-severity vulnerability in shrinerb shrine, published on 5 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15237 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- shrine (RubyGems): affected all versions; fixed in 3.3.0\n- shrine (RubyGems): affected all versions; fixed in 3.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-15237/ (Markdown: https://insights.sbomify.com/CVE-2020-15237/index.md)","id":"CVE-2020-15237","markdown":"https://insights.sbomify.com/CVE-2020-15237/index.md","name":"CVE-2020-15237","record":{"aliases":["GHSA-5jjv-x4fq-qjwp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby file attachment library","requires_auth":"none","summary":"Attackers can guess derivation URL signatures via timing attacks in Shrine's derivation_endpoint plugin, potentially bypassing access controls.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"shrine","vendor":"shrinerb"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Timing attack in Shrine","id":"CVE-2020-15237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Local privilege escalation Blueman","id":"CVE-2020-15238"},"packages":[{"ecosystem":"RubyGems","fixed":["3.3.0"],"introduced":["0"],"last_affected":[],"package":"shrine","purl":null,"source":"GHSA-5jjv-x4fq-qjwp"},{"ecosystem":"RubyGems","fixed":["3.3.0"],"introduced":["0"],"last_affected":[],"package":"shrine","purl":"pkg:gem/shrine","source":"GHSA-5jjv-x4fq-qjwp"}],"prev":{"headline":"Directory Traversal in Wiki.js","id":"CVE-2020-15236"},"products":["shrine"],"published":"2020-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["shrinerb"]},"summary":"Attackers can guess derivation URL signatures via timing attacks in Shrine's derivation_endpoint plugin, potentially bypassing access controls.","url":"https://insights.sbomify.com/CVE-2020-15237/"}