aws-kms-tls-auth
Activity
- Latest release
- 6mo ago
- Total releases
- 3
- Cadence
- ~4 months
- Last 12 months
- 2
Details
- License
- Apache-2.0
- First release
- Jul 15, 2025
| Version | Released | |
|---|---|---|
0.0.3
unknown
|
0.0.3
unknown
Dependencies (21)
+ 13 more |
|
0.0.2
unknown
1 CVE
GHSA-5whh-4q9j-7v28
Mar 03, 2026
aws-kms-tls-auth vulnerable to memory overallocation
3.7
/ 10
Low
Network
High
None
None
Unchanged
None
None
Low
Summaryaws-kms-tls-auth is an optional utility for s2n-tls that enables customers to use AWS KMS keys as part of the PSK extension field in a TLS 1.3 handshake. An issue exists in this library that can lead to overallocation of memory potentially resulting in a denial of service. ImpactThe PSK extension field in TLS 1.3 uses length-prefixed lists to encode variable-length data. aws-kms-tls-auth interprets the length prefix incorrectly resulting in additional memory allocation. s2n-tls limits ClientHello messages to 64 KB. Due to this issue, the server may allocate up to 10× the received size, meaning a single message could trigger an allocation of up to 640 KB. Repeated allocations of this size could exhaust server resources and lead to a denial-of-service. No AWS services are affected. Applications should continue to follow best practices by limiting the number of in-flight handshakes and concurrent connections. Applications using the aws-kms-tls-auth crate should upgrade to version 0.0.3. Impacted versions: < 0.0.3 PatchesThis issue has been addressed in aws-kms-tls-auth v0.0.3 [1]. WorkaroundsThere is no workaround. Applications using aws-kms-tls-auth should upgrade to the most recent release. Acknowledgements2n-tls would like to thank Joshua Rogers (https://joshua.hu/) of AISLE Research Team (https://aisle.com/) for collaborating on this issue through the coordinated disclosure process. If there are any questions or comments about this advisory, contact AWS/Amazon Security via the vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://crates.io/crates/aws-kms-tls-auth/0.0.3 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.0.3
References Updated Mar 04, 2026 · Source: OSV.dev |
0.0.2
unknown
Dependencies (21)
+ 13 more |
|
0.0.1
unknown
1 CVE
GHSA-5whh-4q9j-7v28
Mar 03, 2026
aws-kms-tls-auth vulnerable to memory overallocation
3.7
/ 10
Low
Network
High
None
None
Unchanged
None
None
Low
Summaryaws-kms-tls-auth is an optional utility for s2n-tls that enables customers to use AWS KMS keys as part of the PSK extension field in a TLS 1.3 handshake. An issue exists in this library that can lead to overallocation of memory potentially resulting in a denial of service. ImpactThe PSK extension field in TLS 1.3 uses length-prefixed lists to encode variable-length data. aws-kms-tls-auth interprets the length prefix incorrectly resulting in additional memory allocation. s2n-tls limits ClientHello messages to 64 KB. Due to this issue, the server may allocate up to 10× the received size, meaning a single message could trigger an allocation of up to 640 KB. Repeated allocations of this size could exhaust server resources and lead to a denial-of-service. No AWS services are affected. Applications should continue to follow best practices by limiting the number of in-flight handshakes and concurrent connections. Applications using the aws-kms-tls-auth crate should upgrade to version 0.0.3. Impacted versions: < 0.0.3 PatchesThis issue has been addressed in aws-kms-tls-auth v0.0.3 [1]. WorkaroundsThere is no workaround. Applications using aws-kms-tls-auth should upgrade to the most recent release. Acknowledgements2n-tls would like to thank Joshua Rogers (https://joshua.hu/) of AISLE Research Team (https://aisle.com/) for collaborating on this issue through the coordinated disclosure process. If there are any questions or comments about this advisory, contact AWS/Amazon Security via the vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://crates.io/crates/aws-kms-tls-auth/0.0.3 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.0.3
References Updated Mar 04, 2026 · Source: OSV.dev |
0.0.1
unknown
Dependencies (18)
+ 10 more |