Skip to content

GHSA-vpm6-h53m-x2xf CVE-2012-2153

Drupal improper access restrictions

Medium Packagist
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
1.88%
Chance of exploitation in the next 30 days. Higher than 79.46% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
7.14
Upgrade drupal/drupal to this version or later

Description

Drupal 7.x before 7.14 does not properly restrict access to nodes in a list when using a "contributed node access module," which allows remote authenticated users with the "Access the content overview page" permission to read all published nodes by accessing the admin/content page.

Affected versions

Packagist

PackageVulnerableFixed in
drupal/drupal
>= 7.0, < 7.14
7.14

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

drupal/drupal Packagist → 7.14

composer
composer require drupal/drupal:^7.14

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2020-13671
Drupal core Unrestricted Upload of File with Dangerous Type
High Known exploited Also affects drupal/drupal
CVE-2019-6340
Drupal Core Remote Code Execution Vulnerability
High Known exploited Also affects drupal/drupal
CVE-2018-7602
Drupal Core Remote Code Execution Vulnerability
Critical Known exploited Also affects drupal/drupal
CVE-2018-7600
Drupal Core Remote Code Execution Vulnerability
Critical Known exploited Also affects drupal/drupal
DRUPAL-CORE-2024-008
Drupal core contains a potential PHP Object Injection vulnerability
Critical Also affects drupal/drupal
DRUPAL-CORE-2024-007
Drupal core contains a potential PHP Object Injection vulnerability
Critical Also affects drupal/drupal
DRUPAL-CORE-2024-006
Drupal core contains a potential PHP Object Injection vulnerability
Critical Also affects drupal/drupal
DRUPAL-CORE-2024-004
Drupal core Access bypass
High Also affects drupal/drupal
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor