Поиск уязвимостей
Количество 24
Количество 24
CVE-2026-6368
wordexp with WRDE_APPEND can return or use invalid memory
CVE-2026-6368
Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to v ...
GHSA-cm6j-gmqf-j2cm
Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
GHSA-ch73-g8qv-r6r5
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-6368 wordexp with WRDE_APPEND can return or use invalid memory | 0% Низкий | 3 месяца назад | ||
CVE-2026-6368 Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to v ... | 0% Низкий | 3 месяца назад | ||
GHSA-cm6j-gmqf-j2cm Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process. | 0% Низкий | 3 месяца назад | ||
GHSA-ch73-g8qv-r6r5 When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash. | 0% Низкий | 3 месяца назад |
Уязвимостей на страницу