Vulnerability from drupal
Published
2018-02-21 20:12
Modified
2023-08-11 21:43
Summary
Details

This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.

  • The module doesn't sufficiently associate cacheability metadata in certain situations thereby causing an access bypass vulnerability.

This vulnerability is mitigated by the fact that an attacker cannot trigger an exploitable situation themselves. * The module doesn't sufficiently check access in certain situations.

This vulnerability is mitigated by the fact that an attacker must have permission to create entities of certain content entity types.

Update: This is fixed in 8.x-1.10 not 8.x-1.9

Credits
Aaron Clemmer www.drupal.org/u/acamer32
Gabe Sullice www.drupal.org/user/2287430
Wim Leers www.drupal.org/user/99777
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003c1.10.0"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/jsonapi"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003c1.10.0"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.10.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/acamer32"
      ],
      "name": "Aaron Clemmer"
    },
    {
      "contact": [
        "https://www.drupal.org/user/2287430"
      ],
      "name": "Gabe Sullice"
    },
    {
      "contact": [
        "https://www.drupal.org/user/99777"
      ],
      "name": "Wim Leers"
    }
  ],
  "details": "This module provides a JSON API standards-compliant API for accessing and manipulating Drupal content and configuration entities.\n\n* The module doesn\u0027t sufficiently associate cacheability metadata in certain situations thereby causing an access bypass vulnerability.\n\n  This vulnerability is mitigated by the fact that an attacker cannot trigger an exploitable situation themselves.\n* The module doesn\u0027t sufficiently check access in certain situations.\n\n  This vulnerability is mitigated by the fact that an attacker must have permission to create entities of certain content entity types.\n\n#### Update: This is fixed in 8.x-1.10 not 8.x-1.9",
  "id": "DRUPAL-CONTRIB-2018-015",
  "modified": "2023-08-11T21:43:40.000Z",
  "published": "2018-02-21T20:12:22.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2018-015"
    }
  ],
  "schema_version": "1.7.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.