# GHSA-6ccv-8fgf-cjpw: Drupal core Denial of Service vulnerability

> An attacker can cause a denial of service by sending specific comment reply requests to Drupal sites using the Comment 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:** 12 Feb 2024

## What is GHSA-6ccv-8fgf-cjpw?

GHSA-6ccv-8fgf-cjpw is a denial of service vulnerability in drupal/core, published on 12 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Comment module allows users to reply to comments. In certain cases, an attacker could make comment reply requests that would trigger a denial of service (DOS).

Sites that do not use the Comment module are not affected.

## Which versions are affected by GHSA-6ccv-8fgf-cjpw?

4 open source packages ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 10.2.0 | 10.2.2 |
| `drupal/core` | Packagist | From 10.2.0 | 10.2.2 |
| `drupal/core` | Packagist | From 8.0.0 | 10.1.8 |
| `drupal/core` | Packagist | From 8.0.0 | 10.1.8 |

## How do I fix GHSA-6ccv-8fgf-cjpw?

Upgrade drupal/core to a fixed version for your release line: 10.2.2 or 10.1.8.

## Is GHSA-6ccv-8fgf-cjpw being exploited?

There is no known exploitation of GHSA-6ccv-8fgf-cjpw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6ccv-8fgf-cjpw and fix it if it is affected.

What it is: GHSA-6ccv-8fgf-cjpw is a denial of service vulnerability in drupal/core, published on 12 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-6ccv-8fgf-cjpw in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 10.2.0; fixed in 10.2.2
- drupal/core (Packagist): affected from 10.2.0; fixed in 10.2.2
- drupal/core (Packagist): affected from 8.0.0; fixed in 10.1.8
- drupal/core (Packagist): affected from 8.0.0; fixed in 10.1.8

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/GHSA-6ccv-8fgf-cjpw/ (Markdown: https://insights.sbomify.com/GHSA-6ccv-8fgf-cjpw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6ccv-8fgf-cjpw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6ccv-8fgf-cjpw/
Summaries are generated and may contain mistakes; the official description above is the record.