# DRUPAL-CORE-2019-011: The Media Library module has a security vulnerability whereby it doesn't sufficiently restrict access to media items in certain configurations.

> Attackers with low privileges can access unauthorized media items in specific Drupal configurations, exposing sensitive content.

- **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:** 18 Dec 2019

## What is DRUPAL-CORE-2019-011?

DRUPAL-CORE-2019-011 is a missing authorization vulnerability in drupal/core, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Media Library module has a security vulnerability whereby it doesn't sufficiently restrict access to media items in certain configurations.

## Which versions are affected by DRUPAL-CORE-2019-011?

1 open source package ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 8.0.0 | 8.7.11, 8.8.1 |

## How do I fix DRUPAL-CORE-2019-011?

Upgrade drupal/core to a fixed version for your release line: 8.7.11 or 8.8.1.

## Is DRUPAL-CORE-2019-011 being exploited?

There is no known exploitation of DRUPAL-CORE-2019-011 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CORE-2019-011 and fix it if it is affected.

What it is: DRUPAL-CORE-2019-011 is a missing authorization vulnerability in drupal/core, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CORE-2019-011 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 8.0.0; fixed in 8.7.11, 8.8.1

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-CORE-2019-011/ (Markdown: https://insights.sbomify.com/DRUPAL-CORE-2019-011/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CORE-2019-011

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