Show filters
148 Total Results
Displaying 71-80 of 148
Sort by:
Attacker Value
Unknown

CVE-2021-42376

Disclosure Date: November 15, 2021 (last updated February 23, 2025)
A NULL pointer dereference in Busybox's hush applet leads to denial of service when processing a crafted shell command, due to missing validation after a \x03 delimiter character. This may be used for DoS under very rare conditions of filtered command input.
Attacker Value
Unknown

CVE-2021-42375

Disclosure Date: November 15, 2021 (last updated February 23, 2025)
An incorrect handling of a special element in Busybox's ash applet leads to denial of service when processing a crafted shell command, due to the shell mistaking specific characters for reserved characters. This may be used for DoS under rare conditions of filtered command input.
Attacker Value
Unknown

CVE-2021-42374

Disclosure Date: November 15, 2021 (last updated February 23, 2025)
An out-of-bounds heap read in Busybox's unlzma applet leads to information leak and denial of service when crafted LZMA-compressed input is decompressed. This can be triggered by any applet/format that
Attacker Value
Unknown

CVE-2021-42373

Disclosure Date: November 15, 2021 (last updated February 23, 2025)
A NULL pointer dereference in Busybox's man applet leads to denial of service when a section name is supplied but no page argument is given
Attacker Value
Unknown

CVE-2017-5123

Disclosure Date: November 02, 2021 (last updated February 23, 2025)
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
Attacker Value
Unknown

CVE-2021-43057

Disclosure Date: October 28, 2021 (last updated February 23, 2025)
An issue was discovered in the Linux kernel before 5.14.8. A use-after-free in selinux_ptrace_traceme (aka the SELinux handler for PTRACE_TRACEME) could be used by local attackers to cause memory corruption and escalate privileges, aka CID-a3727a8bac0a. This occurs because of an attempt to access the subjective credentials of another task.
Attacker Value
Unknown

CVE-2021-25219

Disclosure Date: October 27, 2021 (last updated November 08, 2023)
In BIND 9.3.0 -> 9.11.35, 9.12.0 -> 9.16.21, and versions 9.9.3-S1 -> 9.11.35-S1 and 9.16.8-S1 -> 9.16.21-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.18 of the BIND 9.17 development branch, exploitation of broken authoritative servers using a flaw in response processing can cause degradation in BIND resolver performance. The way the lame cache is currently designed makes it possible for its internal data structures to grow almost infinitely, which may cause significant delays in client query processing.
Attacker Value
Unknown

CVE-2021-41182

Disclosure Date: October 26, 2021 (last updated February 23, 2025)
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources.
Attacker Value
Unknown

CVE-2021-41183

Disclosure Date: October 26, 2021 (last updated February 23, 2025)
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources.
Attacker Value
Unknown

CVE-2021-41184

Disclosure Date: October 26, 2021 (last updated February 23, 2025)
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.