nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory w…
nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
https://cwe.mitre.org/data/definitions/119.html →Open in CWE collection →A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.
https://cwe.mitre.org/data/definitions/466.html →Open in CWE collection →The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
https://cwe.mitre.org/data/definitions/703.html →Open in CWE collection →This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An adversary who has knowledge of known vulnerable libraries or shared code can easily target software that makes use of these libraries. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
https://capec.mitre.org/data/definitions/8.html →Open in CAPEC collection →This attack targets command-line utilities available in a number of shells. An adversary can leverage a vulnerability found in a command-line utility to escalate privilege to root.
https://capec.mitre.org/data/definitions/9.html →Open in CAPEC collection →This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
https://capec.mitre.org/data/definitions/10.html →Open in CAPEC collection →This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service. This hostile service is created to deliver the correct content to the client software. For example, if the client-side application is a browser, the service will host a webpage that the browser loads.
https://capec.mitre.org/data/definitions/14.html →Open in CAPEC collection →In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
https://capec.mitre.org/data/definitions/24.html →Open in CAPEC collection →An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
https://capec.mitre.org/data/definitions/42.html →Open in CAPEC collection →An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the adversary access to the execution stack and execute arbitrary code in the target process.
https://capec.mitre.org/data/definitions/44.html →Open in CAPEC collection →This type of attack leverages the use of symbolic links to cause buffer overflows. An adversary can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
https://capec.mitre.org/data/definitions/45.html →Open in CAPEC collection →This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The adversary crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
https://capec.mitre.org/data/definitions/46.html →Open in CAPEC collection →In this attack, the target software is given input that the adversary knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
https://capec.mitre.org/data/definitions/47.html →Open in CAPEC collection →Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
https://capec.mitre.org/data/definitions/100.html →Open in CAPEC collection →An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory.
https://capec.mitre.org/data/definitions/123.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| 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 | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked | |
| glibc | Tracked |