Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2025-54799

Опубликовано: 07 авг. 2025
Источник: redhat
CVSS3: 5.3
EPSS Низкий

Описание

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.

A flaw was found in github.com/go-acme/lego. The LEGO ACME client and library fail to enforce HTTPS communication when interacting with Certificate Authorities, allowing unencrypted data transmission. This vulnerability allows a malicious Certificate Authority or intermediary to intercept and potentially modify ACME requests, leading to eavesdropping and manipulation of the ACME authentication process.

Меры по смягчению последствий

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat OpenShift Dev Spacesdevspaces/configbump-rhel9Will not fix
Red Hat OpenShift Dev Spacesdevspaces/dashboard-rhel9Will not fix
Red Hat OpenShift Dev Spacesdevspaces/devspaces-rhel9-operatorWill not fix
Red Hat OpenShift Dev Spacesdevspaces/imagepuller-rhel9Will not fix
Red Hat OpenShift Dev Spacesdevspaces-tech-preview/jetbrains-ide-rhel9Will not fix
Red Hat OpenShift Dev Spacesdevspaces/traefik-rhel8Not affected
Red Hat OpenShift Dev Spacesdevspaces/traefik-rhel9Will not fix

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-319
https://bugzilla.redhat.com/show_bug.cgi?id=2386975github.com/go-acme/lego: Lego: Unenforced HTTPS Communication Vulnerability

EPSS

Процентиль: 4%
0.00023
Низкий

5.3 Medium

CVSS3

Связанные уязвимости

ubuntu
22 дня назад

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.

nvd
22 дня назад

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.

debian
22 дня назад

Let's Encrypt client and ACME library written in Go (Lego). In version ...

github
22 дня назад

github.com/go-acme/lego/v4/acme/api does not enforce HTTPS

EPSS

Процентиль: 4%
0.00023
Низкий

5.3 Medium

CVSS3