{"answers":{"affected":"","exploited":"There is no known exploitation of DRUPAL-CONTRIB-2022-002 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"DRUPAL-CONTRIB-2022-002 is an authentication bypass vulnerability in drupal/simple_oauth, published on 5 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for DRUPAL-CONTRIB-2022-002 and fix it if it is affected.\n\nWhat it is: DRUPAL-CONTRIB-2022-002 is an authentication bypass vulnerability in drupal/simple_oauth, published on 5 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-002 in the wild and no public exploit code.\n\nAffected product: drupal/simple_oauth. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/DRUPAL-CONTRIB-2022-002/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-002/index.md)","id":"DRUPAL-CONTRIB-2022-002","markdown":"https://insights.sbomify.com/DRUPAL-CONTRIB-2022-002/index.md","name":"DRUPAL-CONTRIB-2022-002","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Drupal OAuth module","requires_auth":"low_privilege","summary":"Insufficient verification of client secrets in Drupal OAuth module allows bypassing confidentiality checks for certain grant types, potentially exposing data.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This module enables you to implement OAuth 2.0 authentication for Drupal.\n\nThe module doesn't sufficiently verify client secret keys for \"confidential\" OAuth 2.0 clients when using certain grant types. The token refresh and client credentials grants are not affected.\n\nThis vulnerability is mitigated by the fact that the vast majority of OAuth 2.0 clients in the wild are public, not confidential. Furthermore, all affected grant types still require users to authenticate to Drupal during the OAuth flow.\n\nThe implicit grant type is insecure for other reasons (and still requires user authentication) and is disabled by default.\n\nSites at risk of information disclosure would be specifically configured to restrict access based on the OAuth client's confidentiality status and configured scopes, not only traditional Drupal user permissions and roles.\n\nFurther mitigation includes [configuring allowed redirect URIs for clients](https://tools.ietf.org/html/rfc6819#section-5.2.3.5). This is an OAuth best practice for guarding against man-in-the-middle attacks on authorization codes, and prevents redirection to imposter clients.\n\nAnyone implementing OAuth 2.0 on their Drupal site is also encouraged to review the [relevant RFCs and Internet-Drafts](https://oauth.net/security/) pertaining to OAuth security.","ecosystems":["Packagist:https://packages.drupal.org/8"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"This module enables you to implement OAuth 2.0 authentication for Drupal.","id":"DRUPAL-CONTRIB-2022-002","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Packagist:https://packages.drupal.org/8","fixed":["4.6.0","5.0.6"],"introduced":["0","5.0.0"],"last_affected":[],"package":"drupal/simple_oauth","purl":"pkg:composer/drupal/simple_oauth?repository_url=https:%2F%2Fpackages.drupal.org%2F8","source":"DRUPAL-CONTRIB-2022-002"}],"products":null,"published":"2022-01-05","related":[],"sources":[{"class":"attribution","licence":"MIT","name":"Drupal","prefix":"DRUPAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Insufficient verification of client secrets in Drupal OAuth module allows bypassing confidentiality checks for certain grant types, potentially exposing data.","url":"https://insights.sbomify.com/DRUPAL-CONTRIB-2022-002/"}