Vulnerabilities

A vulnerability in the Agent Development Kit (ADK) allows for continuation forgery in tool confirmations. An attacker who is able to manipulate or inject events into the session history can execute unauthorized tools by forging a tool confirmation response. This is possible because the framework did not verify if the target tool was registered to the executing agent, did not validate if the tool actually required confirmation, and did not match the confirmation arguments against the original tool call event in the history.

7-Zip XZ Decompression Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of 7-Zip. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.<br /> <br /> The specific flaw exists within the processing of XZ chunked data. Crafted XZ-compressed data can trigger an overflow of a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-30169.

A vulnerability in the `zipx.Unzip` extraction routine of Develar&amp;#39;s app-builder allows an attacker to overwrite arbitrary files on macOS APFS by exploiting a Unicode Normalization Collision combined with symlink following behavior. APFS treats certain Unicode equivalent filenames as identical (e.g., ß ↔ ss), while app builder performs no canonical normalization before validating or writing paths. As a result, a crafted ZIP archive containing:<br /> • a symlink entry named ss pointing to a target file, and<br /> • a regular file named ß containing attacker controlled data,<br /> will cause the second write to follow the symlink and overwrite the target file.

A Spring Security authentication and authorization bypass exists in Coverity Connect versions between 2023.6.0 and 2026.3.0. An unauthenticated malicious threat actor that can send a specially crafted HTTP request is able to bypass authentication and authorization controls on certain API endpoints to access data within Coverity.

A SQL injection vulnerability exists in the Coverity Connect SOAP API for versions between 2024.6.0 and 2026.3.0 (inclusive). A malicious, authenticated threat actor who sends a specially crafted payload can achieve full read access to database contents and other unauthorized commands.

Courier IMAP before 6.0.1 and Courier Mail Server before 2.0.2 allow authenticated IMAP users to crash the imapd process via deeply nested parenthesized SEARCH queries. The SEARCH command parser (alloc_search_key in searchinfo.C) recursively descends on nested parenthesized groups through a mutual recursion chain with alloc_search_andlist() and alloc_search_notkey(), with no depth limit. Courier IMAP has no overall command line length limit, making exploitation trivial. A single IMAP command with ~2500 nested parentheses overflows the 8MB default stack, causing SIGSEGV.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/pkey: Check length in pkey_pckmo handler implementation<br /> <br /> Explicitly check the length of the target buffer in the pkey_pckmo<br /> implementation of the key_to_protkey() handler function. The handler<br /> function fails, if the generated output data exceeds the length of the<br /> provided target buffer.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/pkey: Check length in PKEY_VERIFYPROTK ioctl<br /> <br /> Explicitly check the buffer length request structure provided by<br /> user-space and fail, if it exceeds the buffer size.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> posix-cpu-timers: Prevent UAF caused by non-leader exec() race<br /> <br /> Wongi and Jungwoo decoded and reported a non-leader exec() related race<br /> which can result in an UAF:<br /> <br /> sys_timer_delete() exec()<br /> posix_cpu_timer_del()<br /> // Observes old leader<br /> p = pid_task(pid, pid_type); de_thread()<br /> switch_leader();<br /> release_task(old_leader)<br /> __exit_signal(old_leader)<br /> sighand = lock(old_leader, sighand);<br /> posix_cpu_timers*_exit();<br /> sighand = lock_task_sighand(p) unhash_task(old_leader);<br /> sh = lock(p, sighand) old_leader-&gt;sighand = NULL;<br /> unlock(sighand);<br /> (p-&gt;sighand == NULL)<br /> unlock(sh)<br /> return NULL;<br /> <br /> // Returns without action<br /> if(!sighand)<br /> return 0;<br /> free_posix_timer();<br /> <br /> This is "harmless" unless the deleted timer was armed and enqueued in<br /> p-&gt;signal because on exec() a TGID targeted timer is inherited.<br /> <br /> As sys_timer_delete() freed the underlying posix timer object<br /> run_posix_cpu_timers() or any timerqueue related add/delete operations on<br /> other timers will access the freed object&amp;#39;s timerqueue node, which results<br /> in an UAF.<br /> <br /> There is a similar problem vs. posix_cpu_timer_set(). For regular posix<br /> timers it just transiently returns -ESRCH to user space, but for the use<br /> case in do_cpu_nanosleep() it&amp;#39;s the same UAF just that the k_itimer is<br /> allocated on the stack.<br /> <br /> Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops<br /> to expire.<br /> <br /> While debating solutions Frederic pointed out another problem:<br /> <br /> posix_cpu_timer_del(tmr)<br /> __exit_signal(p)<br /> posix_cpu_timers*_exit(p);<br /> unhash_task(p);<br /> p-&gt;sighand = NULL;<br /> sh = lock_task_sighand(p)<br /> sighand = p-&gt;sighand;<br /> if (!sighand)<br /> return NULL;<br /> lock(sighand);<br /> <br /> if (!sh)<br /> WARN_ON_ONCE(timer_queued(tmr));<br /> <br /> On weakly ordered architectures it is not guaranteed that<br /> posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit()<br /> when p-&gt;sighand is observed as NULL, which means the WARN() can be a false<br /> positive.<br /> <br /> Solve these issues by:<br /> <br /> 1) Changing the store in __exit_signal() to smp_store_release().<br /> <br /> 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path<br /> of lock_task_sighand().<br /> <br /> 3) Creating a helper function for looking up the task and locking sighand<br /> which does not return when sighand == NULL. Instead it retries the<br /> task lookup and only if that fails it gives up.<br /> <br /> 4) Using that helper in the three affected functions.<br /> <br /> #1/#2 ensures that the reader side which observes sighand == NULL also<br /> observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit()<br /> and the ones in unhash_task().<br /> <br /> #3 ensures that the above described non-leader exec() situation is handled<br /> gracefully. When the task lookup returns the old leader, but sighand ==<br /> NULL then it retries. In the non-leader exec() case the subsequent task<br /> lookup will observe the new leader due to #1/#2. In normal exit() scenarios<br /> the subsequent lookup fails.<br /> <br /> When the task lookup fails, the function also checks whether the timer is<br /> still enqueued and issues a warning if that&amp;#39;s the case. Unfortunately there<br /> is nothing which can be done about it, but as the task is already not<br /> longer visible the timer should not be accessed anymore. This check also<br /> requires memory ordering, which is not provided when the first lookup<br /> fails. To achieve that the check is preceeded by a smp_rmb() which pairs<br /> with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that<br /> the stores in posix_cpu_timers*_exit() are visible.<br /> <br /> The history of the non-leader exec() issue goes back to the early days of<br /> posix CPU timers, which stored a pointer to the group leader task in the<br /> timer. That obviously fails when a non-leader exec() switches the leader.<br /> commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems<br /> with mt exec") added a temporary workaround for that in 2010 which surv<br /> ---truncated---

ZITADEL is an open source identity management platform. From 2.43.0 through 2.71.19, from 3.0.0 until 3.4.11, and from 4.0.0 until 4.15.1, the email and phone self-management API paths in internal/command/user_v2_email.go, internal/command/user_v2_phone.go, and internal/command/user_v2_human.go allowed users to request returned verification codes without the required permission, allowing users to claim ownership of email addresses or phone numbers they do not control and bypass email-based or phone-based security policies. This issue is fixed in versions 3.4.11 and 4.15.1.

proot-distro is a utility for managing proot containers. Prior to version 5.1.6, proot-distro restore accepted hardlink entries whose linkname referenced another installed container and did not verify that the hardlink source container matched the destination container being restored, allowing a crafted restore archive to copy files between otherwise isolated containers. This issue is fixed in version 5.1.6.

fuse-overlayfs is an implementation of overlayfs in FUSE for rootless containers. Prior to 1.17, the release-1.x C branch preserves SUID and SGID mode bits in main.c during open(O_TRUNC) and truncate handling on a copied-up file, allowing a low-privileged process to leave the upper-layer file with mode 4777. This issue is fixed in version 1.17.