# DRUPAL-CONTRIB-2019-022: This resolves issues described in [SA-CORE-2019-003](https://www.drupal.org/sa-core-2019-003) for this module.

> This update resolves issues from SA-CORE-2019-003 in a Drupal contrib module, affecting only specific configurations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 20 Feb 2019

## What is DRUPAL-CONTRIB-2019-022?

DRUPAL-CONTRIB-2019-022 is a vulnerability in drupal/video, published on 20 Feb 2019. It can be exploited over the network.

### Official description

This resolves issues described in [SA-CORE-2019-003](https://www.drupal.org/sa-core-2019-003) for this module. Not all configurations are affected. See [SA-CORE-2019-003](https://www.drupal.org/sa-core-2019-003) for details.

## Which versions are affected by DRUPAL-CONTRIB-2019-022?


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

## How do I fix DRUPAL-CONTRIB-2019-022?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-022 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-022 is a vulnerability in drupal/video, published on 20 Feb 2019. It can be exploited over the network.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2019-022 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-022

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