{"answers":{"affected":"8 open source packages ship an affected version, including doorkeeper. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10187 in the wild and no public exploit code.","fix":"Upgrade doorkeeper to a fixed version for your release line: 5.0.3, 5.1.1, 5.2.5 or 5.3.2.","what":"CVE-2020-10187 is a high-severity vulnerability in n/a, published on 4 May 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-10187 and fix it if it is affected.\n\nWhat it is: CVE-2020-10187 is a high-severity vulnerability in n/a, published on 4 May 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-10187 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- doorkeeper (RubyGems): affected from 5.0.0; fixed in 5.0.3\n- doorkeeper (RubyGems): affected from 5.0.0; fixed in 5.0.3\n- doorkeeper (RubyGems): affected from 5.1.0; fixed in 5.1.1\n- doorkeeper (RubyGems): affected from 5.1.0; fixed in 5.1.1\n- doorkeeper (RubyGems): affected from 5.2.0; fixed in 5.2.5\n- doorkeeper (RubyGems): affected from 5.2.0; fixed in 5.2.5\n- doorkeeper (RubyGems): affected from 5.3.0; fixed in 5.3.2\n- doorkeeper (RubyGems): affected from 5.3.0; fixed in 5.3.2\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-10187/ (Markdown: https://insights.sbomify.com/CVE-2020-10187/index.md)","id":"CVE-2020-10187","markdown":"https://insights.sbomify.com/CVE-2020-10187/index.md","name":"CVE-2020-10187","record":{"aliases":["DEBIAN-CVE-2020-10187","GHSA-j7vx-8mqj-cqp9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby OAuth library","requires_auth":"none","summary":"An attacker can retrieve OAuth client secrets by requesting authorized applications in JSON format if the controller is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"doorkeeper","vendor":"doorkeeper_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Doorkeeper version 5.0.0 and later contains an information disclosure vulnerability that allows an attacker to retrieve the client secret only intended for the OAuth application owner. After authorizing the application and allowing access, the attacker simply needs to request the list of their authorized applications in a JSON format (usually GET /oauth/authorized_applications.json). An application is vulnerable if the authorized applications controller is enabled.","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":"Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper","id":"CVE-2020-10187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":8,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-10188"},"packages":[{"ecosystem":"RubyGems","fixed":["5.0.3"],"introduced":["5.0.0"],"last_affected":[],"package":"doorkeeper","purl":null,"source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.0.3"],"introduced":["5.0.0"],"last_affected":[],"package":"doorkeeper","purl":"pkg:gem/doorkeeper","source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.1.1"],"introduced":["5.1.0"],"last_affected":[],"package":"doorkeeper","purl":null,"source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.1.1"],"introduced":["5.1.0"],"last_affected":[],"package":"doorkeeper","purl":"pkg:gem/doorkeeper","source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.2.5"],"introduced":["5.2.0"],"last_affected":[],"package":"doorkeeper","purl":null,"source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.2.5"],"introduced":["5.2.0"],"last_affected":[],"package":"doorkeeper","purl":"pkg:gem/doorkeeper","source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.3.2"],"introduced":["5.3.0"],"last_affected":[],"package":"doorkeeper","purl":null,"source":"GHSA-j7vx-8mqj-cqp9"},{"ecosystem":"RubyGems","fixed":["5.3.2"],"introduced":["5.3.0"],"last_affected":[],"package":"doorkeeper","purl":"pkg:gem/doorkeeper","source":"GHSA-j7vx-8mqj-cqp9"}],"prev":{"headline":"Business logic in n/a","id":"CVE-2020-10185"},"products":["n/a"],"published":"2020-05-04","related":[{"cvss_score":9.1,"headline":"Doorkeeper is vulnerable to replay attacks","id":"CVE-2016-6582","kev_date_added":null,"published":"2017-01-23"},{"cvss_score":7.5,"headline":"Doorkeeper subject to Incorrect Permission Assignment","id":"CVE-2018-1000211","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":6.8,"headline":"Doorkeeper vulnerable to Cross-site Request Forgery","id":"CVE-2014-8144","kev_date_added":null,"published":"2014-12-31"},{"cvss_score":6.1,"headline":"Doorkeeper is vulnerable to stored XSS and code execution","id":"CVE-2018-1000088","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":4.2,"headline":"Doorkeeper Improper Authentication vulnerability","id":"CVE-2023-34246","kev_date_added":null,"published":"2023-06-12"}],"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":["n/a"]},"summary":"An attacker can retrieve OAuth client secrets by requesting authorized applications in JSON format if the controller is enabled.","url":"https://insights.sbomify.com/CVE-2020-10187/"}