{"answers":{"affected":"2 open source packages ship an affected version, including software.amazon.cryptography:aws-database-encryption-sdk-dynamodb.","exploited":"There is no known exploitation of GHSA-72fp-w44g-625q in the wild and no public exploit code.","fix":"Upgrade software.amazon.cryptography:aws-database-encryption-sdk-dynamodb to 3.1.1 or later.","what":"GHSA-72fp-w44g-625q is a vulnerability in software.amazon.cryptography:aws-database-encryption-sdk-dynamodb, published on 9 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-72fp-w44g-625q and fix it if it is affected.\n\nWhat it is: GHSA-72fp-w44g-625q is a vulnerability in software.amazon.cryptography:aws-database-encryption-sdk-dynamodb, published on 9 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-72fp-w44g-625q in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- software.amazon.cryptography:aws-database-encryption-sdk-dynamodb (Maven): affected from 3.0.0; fixed in 3.1.1\n- software.amazon.cryptography:aws-database-encryption-sdk-dynamodb (Maven): affected from 3.0.0; fixed in 3.1.1\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-72fp-w44g-625q/ (Markdown: https://insights.sbomify.com/GHSA-72fp-w44g-625q/index.md)","id":"GHSA-72fp-w44g-625q","markdown":"https://insights.sbomify.com/GHSA-72fp-w44g-625q/index.md","name":"GHSA-72fp-w44g-625q","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"AWS Database Encryption SDK","requires_auth":"none","summary":"Signature validation failures occur for DynamoDB Sets marked SIGN_ONLY, causing read errors and potential denial of service for applications using the library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nThis advisory addresses an issue when a DynamoDB Set attribute is marked as SIGN_ONLY in the AWS Database Encryption SDK (DB-ESDK) for DynamoDB. This also includes when a Set is part of a List or a Map.\n\nDB-ESDK for DynamoDB supports `SIGN_ONLY` and `ENCRYPT_AND_SIGN` attribute actions. In version 3.1.0 and below, when a Set type is assigned a `SIGN_ONLY` attribute action, there is a chance that signature validation of the record containing a Set will fail on read, even if the Set attributes contain the same values. The probability of a failure depends on the order of the elements in the Set combined with how DynamoDB returns this data, which is undefined.\n\nThis update addresses the issue by ensuring that any Set values are canonicalized in the same order while written to DynamoDB as when read back from DynamoDB.\n\n### Patches\nFixed in version 3.1.1 \nWe recommend all users upgrade as soon as possible.\n\n### Workarounds\nNone\n\n### References\nFor more information on how to address records with Sets marked as `SIGN_ONLY` written by versions 3.1.0 and below of DB-ESDK, see [AWS Database Encryption SDK Decrypt with Permute](https://github.com/aws/aws-database-encryption-sdk-dynamodb-java/tree/v3.1.1/DecryptWithPermute)","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Signing DynamoDB Sets when using the AWS Database Encryption SDK.","id":"GHSA-72fp-w44g-625q","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["3.1.1"],"introduced":["3.0.0"],"last_affected":[],"package":"software.amazon.cryptography:aws-database-encryption-sdk-dynamodb","purl":null,"source":"GHSA-72fp-w44g-625q"},{"ecosystem":"Maven","fixed":["3.1.1"],"introduced":["3.0.0"],"last_affected":[],"package":"software.amazon.cryptography:aws-database-encryption-sdk-dynamodb","purl":"pkg:maven/software.amazon.cryptography/aws-database-encryption-sdk-dynamodb","source":"GHSA-72fp-w44g-625q"}],"products":null,"published":"2023-11-09","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":"Signature validation failures occur for DynamoDB Sets marked SIGN_ONLY, causing read errors and potential denial of service for applications using the library.","url":"https://insights.sbomify.com/GHSA-72fp-w44g-625q/"}