Potential URI resolution path traversal in the AWS SDK for PHP

FAIBLE 3.3CVE-2023-51651 · CVE-2025-69820 · GHSA-557v-xcg6-rm5m · Published 22/12/2023 · updated 17/06/2026

En bref

CVE-2023-51651 est une vulnérabilité FAIBLE (CVSS 3.3) touchant github.com/beam-cloud/beta9, aws/aws-sdk-php, aws software development kit (amazon).
Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.38%, plus élevée que 31.6% des vulnérabilités.
Correctif : mettre à jour vers 3.288.1 ou plus récent.

Package	Affected versions	Patched versions
github.com/beam-cloud/beta9 Go	`≤ 0.0.0-20260116162221-c1cd75e813cfall versions`	No fix yet
aws/aws-sdk-php Packagist	`< 3.288.1`	`3.288.1`
aws software development kit amazon	`< 3.288.1`	`3.288.1`

Description

Impact

Within the scope of requests to S3 object keys and/or prefixes containing a Unix double-dot, a URI path traversal is possible. The issue exists in thebuildEndpoint method in the RestSerializer component of the AWS SDK for PHP v3 prior to 3.288.1. The buildEndpoint method relies on the Guzzle Psr7 UriResolver utility, which strips dot segments from the request path in accordance with RFC 3986. Under certain conditions, this could lead to an arbitrary object being accessed.

Versions of the AWS SDK for PHP v3 before 3.288.1 are affected by this issue.

Patches

Upgrade to the AWS SDK for PHP >= 3.288.1, if you are on version < 3.288.1.

References

RFC 3986 - https://datatracker.ietf.org/doc/html/rfc3986

For more information

If you have any questions or comments about this advisory, please contact AWS's Security team.

NVD description

AWS SDK for PHP is the Amazon Web Services software development kit for PHP. Within the scope of requests to S3 object keys and/or prefixes containing a Unix double-dot, a URI path traversal is possible. The issue exists in the `buildEndpoint` method in the RestSerializer component of the AWS SDK for PHP v3 prior to 3.288.1. The `buildEndpoint` method relies on the Guzzle Psr7 UriResolver utility, which strips dot segments from the request path in accordance with RFC 3986. Under certain conditions, this could lead to an arbitrary object being accessed. This issue has been patched in version 3.288.1.