How severe is GHSA-h45p-w933-jxh3?

No CVSS score has been assigned to GHSA-h45p-w933-jxh3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h45p-w933-jxh3?

GHSA-h45p-w933-jxh3 affects the following packages: @aws-crypto/client-browser (npm), @aws-crypto/client-browser (npm), @aws-crypto/client-node (npm), @aws-crypto/client-node (npm). Ecosystems affected: npm.

How do I fix GHSA-h45p-w933-jxh3?

Update @aws-crypto/client-browser to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h45p-w933-jxh3 is resolved across your whole dependency graph.

How do I detect GHSA-h45p-w933-jxh3 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aws-crypto/client-browser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h45p-w933-jxh3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-h45p-w933-jxh3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h45p-w933-jxh3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h45p-w933-jxh3 published, and has it been updated?

GHSA-h45p-w933-jxh3 was published on June 1, 2021 and was last updated on June 1, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Improper Verification of Cryptographic Signature in aws-encryption-sdk-javascriptGHSA-h45p-w933-jxh3

GHSA-h45p-w933-jxh3 is a security vulnerability in @aws-crypto/client-browser. A fix is available for @aws-crypto/client-browser — see the affected versions and patch details below.

Published

Jun 1, 2021

Updated

Jun 1, 2021

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Jun 1, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

📦@aws-crypto/client-browser📦@aws-crypto/client-browser📦@aws-crypto/client-node📦@aws-crypto/client-node

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

This advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages.

This ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validating the ECDSA signature, an actor with trusted KMS permissions to decrypt a message may also be able to encrypt messages. This update introduces a new API for callers who wish to stream only unsigned messages.

For customers who process ESDK messages from untrusted sources, this update also introduces a new configuration to limit the number of Encrypted Data Keys (EDKs) that the ESDK will attempt to process per message. This configuration provides customers with a way to limit the number of AWS KMS Decrypt API calls that the ESDK will make per message. This setting will reject messages with more EDKs than the configured limit.

Finally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.

Patches

Fixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.

Customers leveraging the ESDK’s streaming features have several options to protect signature validation. One is to ensure that client code reads to the end of the stream before using released plaintext. With this release, using the new API for streaming and falling back to the non-streaming decrypt API for signed messages prevents using any plaintext from signed data before the signature is validated. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x

Users processing ESDK messages from untrusted sources should use the new maximum encrypted data keys parameter. See https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x

Workarounds

None

For more information

https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs

https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@aws-crypto/client-browser`	all versions	1.9.0`npm install @aws-crypto/client-browser@1.9.0`
📦npm	`@aws-crypto/client-browser`	≥ 2.0.0&&< 2.2.0	2.2.0`npm install @aws-crypto/client-browser@2.2.0`
📦npm	`@aws-crypto/client-node`	all versions	1.9.0`npm install @aws-crypto/client-node@1.9.0`
📦npm	`@aws-crypto/client-node`	≥ 2.0.0&&< 2.2.0	2.2.0`npm install @aws-crypto/client-node@2.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @aws-crypto/client-browser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @aws-crypto/client-browser to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h45p-w933-jxh3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact This advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. This ESDK supports a streaming mode where callers may stream the plaintext of signed messages before the ECDSA signature is validated. In addition to these signatures, the ESDK uses AES-GCM encryption and all plaintext is verified before being released to a caller. There is no impact on the integrity of the ciphertext or decrypted plaintext, however some callers may rely on the the ECDSA signature for non-repudiation. Without validati

O3 Security · Impact-Aware SCA

Is GHSA-h45p-w933-jxh3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works