{"answers":{"affected":"8 open source packages ship an affected version, including @aws-crypto/client-browser and @aws-crypto/client-node.","exploited":"There is no known exploitation of GHSA-h45p-w933-jxh3 in the wild and no public exploit code.","fix":"Upgrade @aws-crypto/client-browser to a fixed version for your release line: 1.9.0 or 2.2.0.","what":"GHSA-h45p-w933-jxh3 is a vulnerability in @aws-crypto/client-browser, published on 1 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-h45p-w933-jxh3 and fix it if it is affected.\n\nWhat it is: GHSA-h45p-w933-jxh3 is a vulnerability in @aws-crypto/client-browser, published on 1 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-h45p-w933-jxh3 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @aws-crypto/client-browser (npm): affected all versions; fixed in 1.9.0\n- @aws-crypto/client-browser (npm): affected all versions; fixed in 1.9.0\n- @aws-crypto/client-browser (npm): affected from 2.0.0; fixed in 2.2.0\n- @aws-crypto/client-browser (npm): affected from 2.0.0; fixed in 2.2.0\n- @aws-crypto/client-node (npm): affected all versions; fixed in 1.9.0\n- @aws-crypto/client-node (npm): affected all versions; fixed in 1.9.0\n- @aws-crypto/client-node (npm): affected from 2.0.0; fixed in 2.2.0\n- @aws-crypto/client-node (npm): affected from 2.0.0; fixed in 2.2.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-h45p-w933-jxh3/ (Markdown: https://insights.sbomify.com/GHSA-h45p-w933-jxh3/index.md)","id":"GHSA-h45p-w933-jxh3","markdown":"https://insights.sbomify.com/GHSA-h45p-w933-jxh3/index.md","name":"GHSA-h45p-w933-jxh3","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS Encryption SDK","requires_auth":"low_privilege","summary":"Attackers with KMS permissions can bypass ECDSA signature validation in streaming mode, undermining non-repudiation guarantees for signed messages.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nThis advisory addresses several LOW severity issues with streaming signed messages and restricting processing of certain types of invalid messages. \n\nThis 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. \n\nFor 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.\n\nFinally, this update adds early rejection of invalid messages with certain invalid combinations of algorithm suite and header data.\n\n### Patches\n\nFixed in versions 1.9 and 2.2. We recommend that all users upgrade to address these issues.\n\nCustomers 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\n\nUsers 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\n\n### Workarounds\n\nNone\n\n### For more information\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#digital-sigs\n\nhttps://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/about-versions.html#version2.2.x","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Improper Verification of Cryptographic Signature in aws-encryption-sdk-javascript","id":"GHSA-h45p-w933-jxh3","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":8,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"@aws-crypto/client-browser","purl":null,"source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"@aws-crypto/client-browser","purl":"pkg:npm/%40aws-crypto/client-browser","source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"@aws-crypto/client-browser","purl":null,"source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"@aws-crypto/client-browser","purl":"pkg:npm/%40aws-crypto/client-browser","source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"@aws-crypto/client-node","purl":null,"source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"@aws-crypto/client-node","purl":"pkg:npm/%40aws-crypto/client-node","source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"@aws-crypto/client-node","purl":null,"source":"GHSA-h45p-w933-jxh3"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"@aws-crypto/client-node","purl":"pkg:npm/%40aws-crypto/client-node","source":"GHSA-h45p-w933-jxh3"}],"products":null,"published":"2021-06-01","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers with KMS permissions can bypass ECDSA signature validation in streaming mode, undermining non-repudiation guarantees for signed messages.","url":"https://insights.sbomify.com/GHSA-h45p-w933-jxh3/"}