Vulnerabilidades

*** Pendiente de traducción *** Multiple vulnerabilities exist in OpenThread's handling of MLE packets. An authenticated attacker on the same Thread network could send specially crafted packets to cause a denial of service. These issues include triggerable assertion failures and a stack-based buffer overflow.

*** Pendiente de traducción *** Use-After-Free vulnerability in a zircon kernel pager proxy (Fuchsia), which could lead to a Privilege Escalation from Userspace to Kernel (AP)

*** Pendiente de traducción *** The use of<br /> hard-coded cryptographic key vulnerability has been identified in the mesh<br /> functionality of Deco XE75 v3, XE5300 v3.6 and WE10800 v3.6. <br /> A shared RSA-512 mesh group private key is present in the affected<br /> firmware and is used by the mesh protocol for node authentication.  An attacker who obtains the firmware image<br /> and has local network access may be able to authenticate as a mesh node without<br /> possessing a device-specific credential.<br /> <br /> <br /> <br /> <br /> <br /> Successful<br /> exploitation may allow an unauthenticated adjacent attacker to impersonate a<br /> trusted mesh node and bypass mesh node authentication, which may permit unauthorized<br /> changes to device or mesh configuration, affecting confidentiality, integrity<br /> and availability.

*** Pendiente de traducción *** Improper protection against voltage and clock glitches vulnerability in Microchip SAMA5D4 allows Hardware Fault Injection.<br /> <br /> This issue affects SAMA5D4.

*** Pendiente de traducción *** NetworkManager did not apply the private_user restriction to the 802-1x.ca-path and phase2-ca-path directory-valued connection properties. This incomplete fix for CVE-2025-9615 allows an unprivileged local user to point a private WPA-Enterprise (802.1X) connection profile&amp;#39;s CA path at an attacker-controlled directory, bypassing server certificate validation and enabling credential theft via a rogue access point.

*** Pendiente de traducción *** Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in control panel element-search condition handling. A JSON cleanse bypass in condition.config allows Yii behavior/event configuration keys to be interpreted after decoding, enabling command execution as the PHP/web user.

*** Pendiente de traducción *** Netis NC63 firmware through V3.0.0.3327 contains a stack-based buffer overflow vulnerability that allows unauthenticated remote attackers to overwrite saved stack state by supplying an oversized destHost parameter to the ipFilterList=mod action in netis.cgi. Attackers can exploit widthless sscanf conversions that copy user-supplied input into fixed-size stack buffers before authentication is verified, achieving remote code execution as root due to the Boa web server executing the CGI environment with root privileges.

*** Pendiente de traducción *** Netis NC63 firmware through V3.0.0.3327 contains a stack-based buffer overflow vulnerability that allows unauthenticated remote attackers to overwrite saved stack state by submitting an oversized Base64-encoded password to the login handler in /bin/netis.cgi. Attackers can exploit the custom Base64 decoder&amp;#39;s lack of output length validation against the fixed-size stack buffer to achieve remote code execution with root privileges, as the Boa web server executes the CGI environment as root.

*** Pendiente de traducción *** A path traversal vulnerability was found in AWX&amp;#39;s project archive extraction. The project_archive action plugin extracts zip and tar archive members by joining the project directory path with the member filename without performing path normalization, boundary validation, or rejecting directory traversal sequences. A malicious archive containing members with path traversal components can write files to arbitrary locations on the execution node&amp;#39;s filesystem outside the intended project directory. An attacker who controls the archive content, either through a compromised upstream source, a malicious archive URL, or a man-in-the-middle attack on a plain HTTP connection, can achieve arbitrary file writes as the user performing the extraction, potentially leading to remote code execution through mechanisms such as cron files, SSH authorized keys, or playbook content injection.

*** Pendiente de traducción *** A server-side request forgery (SSRF) vulnerability was found in multiple AWX notification backends. The webhook, Mattermost, Rocket.Chat, and Grafana notification backends use notification template URLs as direct HTTP request targets without validating the target address against private, loopback, or reserved IP ranges. An organization notification administrator can create notification templates pointing to internal or loopback addresses, causing the AWX control node to issue HTTP requests to services that are not externally accessible. Additionally, the webhook notification backend follows HTTP redirects and resends configured Basic Authentication credentials to redirect targets regardless of host change, allowing an attacker to exfiltrate notification credentials by redirecting to an attacker-controlled host. The Grafana backend sends its API key in the Authorization header to the configured target URL.

*** Pendiente de traducción *** BookStack before 26.05.4 contains a broken access control vulnerability that allows authenticated API users with image-update or image-delete permissions to manipulate other users&amp;#39; avatars by exploiting missing content-type restrictions in the Image Gallery API endpoints. Attackers can supply a user avatar&amp;#39;s ID to the API controller, which loads any image type without the web controller&amp;#39;s gallery and drawio restrictions, and when the avatar&amp;#39;s uploaded_to field matches a page ID accessible to the attacker, the authorization check passes allowing the attacker to rename, replace, or delete the target user&amp;#39;s avatar without requiring user-management permission.

*** Pendiente de traducción *** The Zephyr virtio driver does not validate the descriptor-chain head id that the virtio device writes into the used ring. In virtio_isr() (drivers/virtio/virtio_common.c), the device-written vq-&gt;used-&gt;ring[idx].id is used directly as an index into vq-&gt;recv_cbs[] and vq-&gt;desc[], which are both allocated with exactly vq-&gt;num entries. recv_cbs[] holds {cb, opaque} callback entries, and the indexed callback pointer is then invoked as cbe.cb(cbe.opaque, used_len).<br /> <br /> Because the id is consumed as a 16-bit value with no bound check, a malicious or compromised virtio backend (an untrusted hypervisor, or an untrusted hardware/peer-processor virtio device on a PCI or MMIO transport) can supply an id far beyond vq-&gt;num. This causes an out-of-bounds read of a {function pointer, argument} pair from heap memory beyond recv_cbs[], after which the driver calls that attacker-shaped pointer in the guest&amp;#39;s interrupt context. No guest privileges or user interaction are required; the backend triggers it by writing the shared used ring and raising the queue interrupt.<br /> <br /> The result is an arbitrary / attacker-influenced function-pointer call in the Zephyr guest, i.e. a control-flow-hijack primitive that can lead to code execution or, at minimum, a reliable crash. The fix rejects any used-ring id &gt;= vq-&gt;num before indexing recv_cbs[]/desc[] or invoking the callback. This affects builds using CONFIG_VIRTIO with the PCI or MMIO transport.