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

exploitDog

redhat логотип

CVE-2026-42008

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

Описание

Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.

A flaw was found in Dovecot. Forwarded information from a host listed as a trusted proxy is not properly separated from Dovecot's internal authentication fields. This allows a malicious host configured as a trusted proxy to inject values as internal authentication fields, enabling it to authenticate as any user without knowing their password. This vulnerability leads to unauthorized access and affects deployments where the password database honors a field that permits passwordless authentication.

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

To mitigate this issue, ensure that the auth_proxy_trusted_networks configuration in Dovecot is strictly limited to only trusted hosts that are fully under administrative control. Review and restrict the auth_proxy_trusted_networks setting in your Dovecot configuration (e.g., /etc/dovecot/conf.d/10-auth.conf or similar) to prevent unauthorized hosts from acting as trusted proxies. If trusted proxies are not required, remove this configuration entirely. A restart of the Dovecot service may be required for changes to take effect.

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

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 10dovecotFix deferred
Red Hat Enterprise Linux 6dovecotOut of support scope
Red Hat Enterprise Linux 7dovecotFix deferred
Red Hat Enterprise Linux 8dovecotFix deferred
Red Hat Enterprise Linux 9dovecotFix deferred

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

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

Статус:

Moderate
Дефект:
CWE-349
https://bugzilla.redhat.com/show_bug.cgi?id=2525575dovecot: Dovecot: Authentication bypass via trusted proxy forwarding

EPSS

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

4.3 Medium

CVSS3

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

CVSS3: 4.3
ubuntu
16 дней назад

Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.

CVSS3: 4.3
nvd
16 дней назад

Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.

CVSS3: 4.3
debian
16 дней назад

Forwarding information received from a host listed as a trusted proxy ...

CVSS3: 4.3
github
16 дней назад

Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.

suse-cvrf
12 дней назад

Security update for dovecot24

EPSS

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

4.3 Medium

CVSS3