Cleartext Transmission of Sensitive Information Affecting terraform-provider-acme-fips package, versions <2.35.0-r1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-TERRAFORMPROVIDERACMEFIPS-11539926
- published8 Aug 2025
- disclosed7 Aug 2025
Introduced: 7 Aug 2025
NewCVE-2025-54799 (opens in a new tab)How to fix?
Upgrade Chainguard terraform-provider-acme-fips to version 2.35.0-r1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream terraform-provider-acme-fips package and not the terraform-provider-acme-fips package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Let's Encrypt client and ACME library written in Go (Lego). In versions 4.25.1 and below, the github.com/go-acme/lego/v4/acme/api package (thus the lego library and the lego cli as well) don't enforce HTTPS when talking to CAs as an ACME client. Unlike the http-01 challenge which solves an ACME challenge over unencrypted HTTP, the ACME protocol requires HTTPS when a client communicates with the CA to performs ACME functions. However, the library fails to enforce HTTPS both in the original discover URL (configured by the library user) and in the subsequent addresses returned by the CAs in the directory and order objects. If users input HTTP URLs or CAs misconfigure endpoints, protocol operations occur over HTTP instead of HTTPS. This compromises privacy by exposing request/response details like account and request identifiers to network attackers. This was fixed in version 4.25.2.