# DRUPAL-CONTRIB-2018-022: This module enables you to monitor and manage any number of remote Drupal sites and aggregate useful information for administrators in a central dashboard.

> Unauthenticated attackers can achieve remote code execution via PHP object injection in the Drupal Remote Dashboard module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2018

## What is DRUPAL-CONTRIB-2018-022?

DRUPAL-CONTRIB-2018-022 is an unsafe deserialization vulnerability in drupal/drd_agent, published on 25 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables you to monitor and manage any number of remote Drupal sites and aggregate useful information for administrators in a central dashboard.

The modules (DRD and DRD Agent) encrypt the data which is exchanged between them but in order to do so, they use the PHP serialize/unserialize functions instead of the json\_encode/json\_decode combination. As the unserialize function is called on unauthenticated content, this introduces a PHP object injection vulnerability.

## Which versions are affected by DRUPAL-CONTRIB-2018-022?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/drd_agent` | Packagist:https://packages.drupal.org/8 | All versions | 3.7.0 |

## How do I fix DRUPAL-CONTRIB-2018-022?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2018-022 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2018-022 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2018-022 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2018-022 is an unsafe deserialization vulnerability in drupal/drd_agent, published on 25 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2018-022 in the wild and no public exploit code.

Affected product: drupal/drd_agent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2018-022/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2018-022/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2018-022

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2018-022/
Summaries are generated and may contain mistakes; the official description above is the record.