Описание
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the GET handler, or when an Authorization: Negotiate header is supplied, the response is includes a logical.Auth object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of sys/raw. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn't possible to deny access to it.
A flaw was found in OpenBao, an identity-based secrets management system. When the Kerberos authentication method processes a GET request or an Authorization: Negotiate header, it inadvertently creates authentication tokens that are not accessible to the caller and are hidden by an error message. These unaccessible tokens accumulate, potentially leading to a denial of service (DoS) by consuming system resources. A remote, unauthenticated attacker could trigger this condition.
Отчет
Red Hat products do not ship the OpenBao server. Some products bundle the OpenBao API client library (github.com/openbao/openbao/api/v2) as a Go dependency, but this client module does not contain the vulnerable server-side Kerberos authentication handler where token accumulation occurs. The community packages (Fedora, EPEL) ship OpenBao 2.6.1 which includes the fix (2.5.4).
Меры по смягчению последствий
Update OpenBao to version 2.5.4 or later, which limits Kerberos authentication token accumulation.
Ссылки на источники
Дополнительная информация
Статус:
5.3 Medium
CVSS3
Связанные уязвимости
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn't possible to deny access to it.
OpenBao is an open source identity-based secrets management system. Pr ...
OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens
Уязвимость системы управления секретами и шифрованием OpenBao, связанная с ошибками разграничения доступа, позволяющая нарушителю вызвать отказ в обслуживании
5.3 Medium
CVSS3