Vulnerability from drupal – Published: 2018-12-19 17:53 – Updated: 2023-08-11 21:10 – Source website
This module provides a JSON:API specification-compliant HTTP API for accessing and manipulating Drupal content and configuration entities.
The module doesn't sufficiently check access when responding to certain filtered collection requests, thereby causing an access bypass vulnerability. (This means certain GET requests are vulnerable; no POST, PATCH or DELETE requests are vulnerable.)
In order to fix this issue, two new hooks were added: hook_jsonapi_ENTITY_TYPE_filter_access() and hook_jsonapi_entity_field_filter_access(). Sites with custom entity types and/or with entity or field access customizations may need to implement these newly introduced hooks.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.24.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/jsonapi"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.24.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.24.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [],
"credits": [
{
"contact": [
"https://www.drupal.org/user/2287430"
],
"name": "Gabe Sullice"
},
{
"contact": [
"https://www.drupal.org/user/1078742"
],
"name": "Lauri Eskola"
}
],
"details": "This module provides a JSON:API specification-compliant HTTP API for accessing and manipulating Drupal content and configuration entities.\n\nThe module doesn\u0027t sufficiently check access when responding to certain filtered collection requests, thereby causing an access bypass vulnerability. (This means certain `GET` requests are vulnerable; no `POST`, `PATCH` or `DELETE` requests are vulnerable.)\n\nIn order to fix this issue, two new hooks were added: `hook_jsonapi_ENTITY_TYPE_filter_access()` and `hook_jsonapi_entity_field_filter_access()`. Sites with custom entity types and/or with entity or field access customizations may need to implement these newly introduced hooks.",
"id": "DRUPAL-CONTRIB-2018-081",
"modified": "2023-08-11T21:10:49.000Z",
"published": "2018-12-19T17:53:49.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2018-081"
}
],
"schema_version": "1.7.0"
}
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.
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.