Signing DynamoDB Sets when using the AWS Database Encryption SDK.

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact This advisory addresses an issue when a DynamoDB Set attribute is marked as SIGNONLY in the AWS Database Encryption SDK (DB-ESDK) for DynamoDB. This also includes when a Set is part of a List or a Map. DB-ESDK for DynamoDB supports SIGNONLY and ENCRYPTANDSIGN attribute actions. In version 3.1.0 and below, when a Set type is assigned a SIGNONLY 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. This 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. Patches Fixed in version 3.1.1 We recommend all users upgrade as soon as possible. Workarounds None References For more information on how to address records with Sets marked as…

Published by the source

9 Nov 2023, 16:02 UTC

Last modified by the source

9 Nov 2023, 16:02 UTC

Source last checked

26 Oct 2026, 16:16 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-72fp-w44g-625q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-72fp-w44g-625q

Advisory: Signing DynamoDB Sets when using the AWS Database Encryption SDK.
IDs: GHSA-72fp-w44g-625q
Record: https://patchnext.com/advisories/ghsa-72fp-w44g-625q (revision 1, source checked 26 Oct 2026, 16:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: software.amazon.cryptography:aws-database-encryption-sdk-dynamodb 3.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven software.amazon.cryptography:aws-database-encryption-sdk-dynamodb: affected >= 3.0.0, < 3.1.1; fixed in 3.1.1

## Suggested inspection (read-only)
- Maven software.amazon.cryptography:aws-database-encryption-sdk-dynamodb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on software.amazon.cryptography:aws-database-encryption-sdk-dynamodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-72fp-w44g-625q (GitHub-reviewed advisory GHSA-72fp-w44g-625q lists affected ranges: Maven software.amazon.cryptography:aws-database-encryption-sdk-dynamodb >=3.0.0 <3.1.1)

Commands are suggestions: review each one before running it.