Update module github.com/go-acme/lego/v4 to v4.25.2 [SECURITY] #714
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4.13.3
->v4.25.2
GitHub Vulnerability Alerts
CVE-2025-54799
Summary
It was discovered that 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.
Details
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. This is stated in 6.1 of RFC 8555: https://datatracker.ietf.org/doc/html/rfc8555#section-6.1
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 the library user accidentally inputs an HTTP URL, or the CA similarly misconfigures its endpoints, this will cause the relevant parts of the protocol to be performed over HTTP. This can result, at the very least, in a lost of privacy of the request/response details, such as account and request identifiers (which could be intercepted by an attacker in a privileged network position). We did not investigate whether other more serious threats could result from the ability to impersonate a CA for some of the protocol requests, but enforcing HTTPS usage is definitely the safe choice.
Reproducing
This is illustrated in the attached http_acme_test.go. Since it uses private field Core.directory, this test must be placed inside the source directory of https://github.com/go-acme/lego/v4/acme/api to run.
Please note that this only checks getting the directory and creating a new account, but other ACME functions are likely impacted as well, such as creating orders, getting and checking order authorizations.
_
Release Notes
go-acme/lego (github.com/go-acme/lego/v4)
v4.25.2
Compare Source
Changed
Fixed
v4.25.1
Compare Source
Fixed
v4.25.0
Compare Source
The binary size of this release is about ~50% smaller compared to previous releases.
This will also reduce the module cache usage by 320 MB (this will only affect users of lego as a library or who build lego themselves).
Added
Changed
Fixed
v4.24.0
Compare Source
Added
Changed
Fixed
v4.23.1
Compare Source
Due to an error related to Snapcraft, some artifacts of the v4.23.0 release have not been published.
This release contains the same things as v4.23.0.
v4.23.0
Compare Source
Added
Changed
Fixed
alreadyReplaced
errorReturnInfo
v4.22.2
Compare Source
Fixed
v4.22.1
Compare Source
Fixed
Added
v4.22.0
Compare Source
Added
--private-key
flag to set the private key.LEGO_DEBUG_ACME_HTTP_CLIENT
environment variable to debug the calls to the ACME server.LEGO_EMAIL
environment variable for specifying email.--hook-timeout
flag to run and renew commands.--http.delay
option for HTTP challenge.Changed
Removed
Fixed
v4.21.0
Compare Source
Added
Fixed
v4.20.4
Compare Source
Publish the Snap to the Snapcraft stable channel.
v4.20.3
Compare Source
Fixed
v4.20.2
Compare Source
Added
Changed
Fixed
v4.20.1
Compare Source
Cancelled due to CI failure.
v4.20.0
Compare Source
Cancelled due to CI failure.
v4.19.2
Compare Source
Fixed
v4.19.1
Compare Source
Fixed
v4.19.0
Compare Source
Added
dns.propagation-rns
optiondns.propagation-wait
flagPropagationWait
functionChanged
dns.disable-cp
, replaced bydns.propagation-disable-ans
.Fixed
v4.18.0
Compare Source
Added
Changed
Fixed
v4.17.4
Compare Source
Fixed
v4.17.3
Compare Source
Added
Changed
Fixed
v4.17.2
Compare Source
Canceled due to a release failure related to Snapcraft.
The Snapcraft release are disabled for now.
v4.17.1
Compare Source
Canceled due to a release failure related to oci-go-sdk.
The module
github.com/oracle/oci-go-sdk/v65
usesgithub.com/gofrs/flock
but flock doesn't support some platform (like Solaris):Due to that we will remove the Solaris build.
v4.17.0
Compare Source
Canceled due to a release failure related to Snapcraft.
v4.16.1
Compare Source
Fixed
v4.16.0
Compare Source
Added
Changed
Fixed
v4.15.0
Compare Source
Added
Changed
Fixed
v4.14.2
Compare Source
Changelog
a6ddcac
Prepare release v4.14.25ef996e
chore: temporary workaround8a7fd67
Detach v4.14.1v4.14.1
Compare Source
Fixed
v4.14.0
Compare Source
Added
Changed
Fixed
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.