# DRUPAL-CONTRIB-2017-083: Custom Permissions is a lightweight module that allows permissions to be created and managed through an administrative form.

> Authenticated users can bypass custom access controls on protected pages by triggering cache rebuilds in the Custom Permissions module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2017

## What is DRUPAL-CONTRIB-2017-083?

DRUPAL-CONTRIB-2017-083 is an authentication bypass vulnerability in drupal/config_perms, published on 8 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Custom Permissions is a lightweight module that allows permissions to be created and managed through an administrative form.

When this module is in use, any user who is able to perform an action which rebuilds some of Drupal's caches can trigger a scenario in which certain pages protected by this module's custom permissions temporarily lose those custom access controls, thereby leading to an access bypass vulnerability.

## Which versions are affected by DRUPAL-CONTRIB-2017-083?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/config_perms` | Packagist:https://packages.drupal.org/8 | All versions | 1.1.0 |

## How do I fix DRUPAL-CONTRIB-2017-083?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2017-083 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2017-083 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2017-083 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2017-083 is an authentication bypass vulnerability in drupal/config_perms, published on 8 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2017-083 in the wild and no public exploit code.

Affected product: drupal/config_perms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2017-083/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2017-083/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2017-083

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2017-083/
Summaries are generated and may contain mistakes; the official description above is the record.