A memory leak in glibc 2.1.1 (released on May 24, 1999) can be reached and amplified through the LD_HWCAP_MASK environment variable. Please…
A memory leak in glibc 2.1.1 (released on May 24, 1999) can be reached and amplified through the LD_HWCAP_MASK environment variable. Please note that many versions of glibc are not vulnerable to this issue if patched for CVE-2017-1000366.
The product does not properly control the allocation and maintenance of a limited resource.
https://cwe.mitre.org/data/definitions/400.html →Open in CWE collection →The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
https://cwe.mitre.org/data/definitions/772.html →Open in CWE collection →An attacker initiates a resource depletion attack where a large number of small XML messages are delivered at a sufficiently rapid rate to cause a denial of service or crash of the target. Transactions such as repetitive SOAP transactions can deplete resources faster than a simple flooding attack because of the additional resources used by the SOAP protocol and the resources necessary to process SOAP messages. The transactions used are immaterial as long as they cause resource utilization on the target. In other words, this is a normal flooding attack augmented by using messages that will require extra processing on the target.
https://capec.mitre.org/data/definitions/147.html →Open in CAPEC collection →An adversary attempts to deny legitimate users access to a resource by continually engaging a specific resource in an attempt to keep the resource tied up as long as possible. The adversary's primary goal is not to crash or flood the target, which would alert defenders; rather it is to repeatedly perform actions or abuse algorithmic flaws such that a given resource is tied up and not available to a legitimate user. By carefully crafting a requests that keep the resource engaged through what is seemingly benign requests, legitimate users are limited or completely denied access to the resource.
https://capec.mitre.org/data/definitions/227.html →Open in CAPEC collection →An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.
https://capec.mitre.org/data/definitions/469.html →Open in CAPEC collection →An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.
https://capec.mitre.org/data/definitions/492.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| eglibc | Tracked | |
| eglibc | Tracked | |
| eglibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | * | Tracked |