# DRUPAL-CONTRIB-2022-045: The Apigee Edge module allows connecting a Drupal site to Apigee X / Edge in order to build a developer portal.

> Attackers can view cached API keys from the browser cache after a developer logs in on the same computer, exposing sensitive credentials.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 May 2022

## What is DRUPAL-CONTRIB-2022-045?

DRUPAL-CONTRIB-2022-045 is a vulnerability in drupal/apigee_edge, published on 25 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Apigee Edge module allows connecting a Drupal site to Apigee X / Edge in order to build a developer portal. The developers (user) can view API keys for their respective Apps.

The module discloses information by allowing attackers to view cached information of API Keys from the browser cache for a limited time frame after the user login on the same computer.

## Which versions are affected by DRUPAL-CONTRIB-2022-045?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/apigee_edge` | Packagist:https://packages.drupal.org/8 | All versions | 1.26.0, 2.0.3 |

## How do I fix DRUPAL-CONTRIB-2022-045?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2022-045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-045 is a vulnerability in drupal/apigee_edge, published on 25 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-045 in the wild and no public exploit code.

Affected product: drupal/apigee_edge. 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-2022-045/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-045/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-045

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