Skip to content
Fencer Intel
no cvss —

DRUPAL-CONTRIB-2022-002 json

This module enables you to implement OAuth 2.0 authentication for Drupal.

published 4y ago modified 2mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

This module enables you to implement OAuth 2.0 authentication for Drupal.

The 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.

This 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.

The implicit grant type is insecure for other reasons (and still requires user authentication) and is disabled by default.

Sites 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.

Further 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.

Anyone 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.

Patch / fix

  • packagist drupal/simple_oauth 4.6.0, 5.0.6

Is DRUPAL-CONTRIB-2022-002 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist drupal/simple_oauth
<4.6.0
>=5.0.0, <5.0.6
4.6.0
5.0.6

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.