Skip to content

feat: update advisories #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
G-Rath merged 1 commit into from
Oct 29, 2025
Merged

feat: update advisories #141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions advisories/simple_oauth/DSA-CONTRIB-2025-114.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
{
"schema_version": "1.7.0",
"id": "DSA-CONTRIB-2025-114",
"modified": "2025-10-29T17:53:22.000Z",
"modified": "2025-10-29T20:15:52.000Z",
"published": "2025-10-29T16:44:39.000Z",
"aliases": [
"CVE-2025-12466"
],
"details": "This module introduces an OAuth 2.0 authorization server, which can be configured to protect your Drupal instance with access tokens, or allow clients to request new access tokens and refresh them.\n\nThe module doesn't sufficiently respect granted scopes, it affects all access checks that are based on roles. For example: routes that have the `_role` requirement, can be bypassed with an access token.\n\nThis vulnerability is mitigated by the fact that an attacker must have the access token in possession and the user related to the token must have the associated (role requirement) roles assigned.",
"details": "This module introduces an OAuth 2.0 authorization server, which can be configured to protect your Drupal instance with access tokens, or allow clients to request new access tokens and refresh them.\n\nThe module doesn't sufficiently respect granted scopes, it affects all access checks that are based on roles. For example: routes that have the `_role` requirement, can be bypassed with an access token.\n\nThis vulnerability is mitigated by the fact that an attacker must have the access token in possession and the user related to the token must have the associated (role requirement) roles assigned.\n\n*Update: the Affected versions field was updated to reflect that this vulnerability was present in the 6.0.0 release and fixed in 6.0.7. Earlier versions of this advisory incorrectly stated that other versions were affected.*",
"affected": [
{
"package": {
Expand Down