GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate this is being treated as a non-security bug and no real threat.
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 |
|---|---|---|---|
| Glibc | Gnu | - (including) | - (including) |
| Eglibc | Ubuntu | esm-infra-legacy/trusty | * |
| Eglibc | Ubuntu | precise/esm | * |
| Eglibc | Ubuntu | trusty | * |
| Eglibc | Ubuntu | trusty/esm | * |
| Glibc | Ubuntu | bionic | * |
| Glibc | Ubuntu | cosmic | * |
| Glibc | Ubuntu | devel | * |
| Glibc | Ubuntu | disco | * |
| Glibc | Ubuntu | eoan | * |
| Glibc | Ubuntu | esm-infra/bionic | * |
| Glibc | Ubuntu | esm-infra/xenial | * |
| Glibc | Ubuntu | focal | * |
| Glibc | Ubuntu | xenial | * |
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.