Read the docs
TI-2020-19436 Aliases GHSA-53mj-mc38-q894

Remote Memory Exposure in openwhisk

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

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.

Why it matters now

Fix Fixed openwhisk (npm): 3.3.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—openwhisk (npm)before 3.3.13.3.1Patch availableGHSA-53mj-mc38-q894
  • openwhisk (npm) Vendor— Affected before 3.3.1 Fixed in 3.3.1 Patch available GHSA-53mj-mc38-q894

Remediation

  • Fix · GHSA-53mj-mc38-q894 openwhisk (npm) Fixed in 3.3.1 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-53mj-mc38-q894

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences