undicis cache interceptor does not handle the Set-Cookie response header anywhere in its cache path, so it neither refuses to store nor strips that header. In shared cache mode, which is the default, an otherwise cacheable response that carries a Set-Cookie header, for example one marked with a public and max-age directive, is stored and then re-served to a later caller that matches the same cache key. As a result one callers cookie is disclosed to a different caller, and an untrusted server can inject cookies into cached responses served to all subsequent callers. This violates the requirement that a shared cache must not store cookies. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Undici | Nodejs | 7.0.0 (including) | 7.29.1 (excluding) |
| Undici | Nodejs | 8.0.0 (including) | 8.10.2 (excluding) |
| Red Hat Hardened Images | RedHat | nodejs26-main-11.19.0-1.26.7.0.1.5.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs26-main-26.7.0-1.5.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-11.16.0-1.24.18.1.0.2.2.hum1 | * |
| Red Hat Hardened Images | RedHat | nodejs24-main-24.18.1-0.2.2.hum1 | * |
| Red Hat Hardened Images | RedHat | grafana12-4-main-12.4.10-0.2.hum1 | * |
| Node-undici | Ubuntu | upstream | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.