# DRUPAL-CONTRIB-2018-016: This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.

> An attacker with view permissions can bypass access controls to read related Drupal content and configuration entities via the JSON API.

- **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:** 21 Mar 2018

## What is DRUPAL-CONTRIB-2018-016?

DRUPAL-CONTRIB-2018-016 is a missing authorization vulnerability in drupal/jsonapi, published on 21 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.

The module doesn't sufficiently check access when viewing related resources or relationships, thereby causing an access bypass vulnerability.

This vulnerability is mitigated by the fact that an attacker must be allowed to view the related data, otherwise all they can glean is an entity type UUID and a UUID, which are meaningless by themselves.

## Which versions are affected by DRUPAL-CONTRIB-2018-016?


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

## How do I fix DRUPAL-CONTRIB-2018-016?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2018-016 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-016 is a missing authorization vulnerability in drupal/jsonapi, published on 21 Mar 2018. 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-2018-016 in the wild and no public exploit code.

Affected product: drupal/jsonapi. 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-2018-016/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2018-016/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2018-016

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