GHSA-ph2j-5hxq-gxrr CVE-2008-4793
Drupal Node Validation Bypass in the node module API
- Severity
- High
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 2.21%
- Chance of exploitation in the next 30 days. Higher than 82.58% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-284 Improper Access Control
- Fix
5.11- Upgrade drupal/drupal to this version or later
Description
The node module API in Drupal 5.x before 5.11 allows remote attackers to bypass node validation and have unspecified other impact via unknown vectors related to contributed modules.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| drupal/drupal | >= 5.0, < 5.11 |
5.11 |
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 → 5.11
- composer
composer require drupal/drupal:^5.11
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
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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