# GHSA-53mj-mc38-q894: Remote Memory Exposure in openwhisk

> An attacker can trigger remote memory exposure in the OpenWhisk library by supplying a number as the API key, leaking uninitialized memory contents.

- **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:** 1 Sep 2020

## What is GHSA-53mj-mc38-q894?

GHSA-53mj-mc38-q894 is a vulnerability in openwhisk, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `openwhisk` before 3.3.1 are vulnerable to remote memory exposure.

When a number is passed to `api_key`, affected versions of `openwhisk` allocate an uninitialized buffer and send that over network in Authorization header (base64-encoded).

Proof of concept:

```js
var openwhisk = require('openwhisk');
var options = {
  apihost: '127.0.0.1:1433', 
  api_key: USERSUPPLIEDINPUT // number
};
var ow = openwhisk(options);
ow.actions.invoke({actionName: 'sample'}).then(result => console.log(result))
```

## Recommendation

Update to version 3.3.1 or later.

## Which versions are affected by GHSA-53mj-mc38-q894?

2 open source packages ship an affected version, including openwhisk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openwhisk` | npm | All versions | 3.3.1 |
| `openwhisk` | npm | All versions | 3.3.1 |

## How do I fix GHSA-53mj-mc38-q894?

Upgrade openwhisk to 3.3.1 or later.

## Is GHSA-53mj-mc38-q894 being exploited?

There is no known exploitation of GHSA-53mj-mc38-q894 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-53mj-mc38-q894 and fix it if it is affected.

What it is: GHSA-53mj-mc38-q894 is a vulnerability in openwhisk, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-53mj-mc38-q894 in the wild and no public exploit code.

Affected packages and fixed versions:
- openwhisk (npm): affected all versions; fixed in 3.3.1
- openwhisk (npm): affected all versions; fixed in 3.3.1

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/GHSA-53mj-mc38-q894/ (Markdown: https://insights.sbomify.com/GHSA-53mj-mc38-q894/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-53mj-mc38-q894

---
From sbomify Insights: https://insights.sbomify.com/GHSA-53mj-mc38-q894/
Summaries are generated and may contain mistakes; the official description above is the record.