(CVE-2024-13275)
Vulnerability from drupal – Published: 2024-09-11 16:21 – Updated: 2025-02-20 19:22 – Source websiteThis module provides Drupal with various security-hardening options, for example by emitting various configurable HTTP response headers.
The module doesn't sufficiently validate input in Content Security Policy (CSP) violation reports. This can cause errors when a logging module (e.g. dblog or syslog) attempts to parse the resulting log message which contains invalid data.
This vulnerability is mitigated by the fact that to be affected a site must have seckit's CSP reporting functionality enabled. Recent versions of Drupal 10 and 11 core are not vulnerable due to improved parsing of log messages.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c2.0.3"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/seckit"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c2.0.3"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "2.0.3"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2024-13275"
],
"credits": [
{
"contact": [
"https://www.drupal.org/user/3827467"
],
"name": "_b0lli"
}
],
"details": "This module provides Drupal with various security-hardening options, for example by emitting various configurable HTTP response headers.\n\nThe module doesn\u0027t sufficiently validate input in Content Security Policy (CSP) violation reports. This can cause errors when a logging module (e.g. dblog or syslog) attempts to parse the resulting log message which contains invalid data.\n\nThis vulnerability is mitigated by the fact that to be affected a site must have seckit\u0027s CSP reporting functionality enabled. Recent versions of Drupal 10 and 11 core are not vulnerable due to [improved parsing of log messages](https://www.drupal.org/project/drupal/issues/2481349).",
"id": "DRUPAL-CONTRIB-2024-039",
"modified": "2025-02-20T19:22:14.000Z",
"published": "2024-09-11T16:21:22.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2024-039"
}
],
"schema_version": "1.7.0"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.