Hírolvasó

Overview

A heap-based buffer overflow exists in the Tight JPEG decoding component of the TightVNC Windows Viewer version 1.3.10 and affected UltraVNC Windows Viewers. An attacker controlling a malicious VNC server can trigger memory corruption by sending a specially crafted screen update. Successful exploitation can crash the viewer and may allow arbitrary code execution, although only denial of service conditions were demonstrated during testing.

Description

TightVNC and UltraVNC provide remote desktop access using the Remote Framebuffer (RFB) protocol. Their viewer applications connect to VNC servers and decode screen updates for local display. Tight encoding supports JPEG compression of image data within these updates.

The Windows viewer function DecompressJpegRect() allocates a heap buffer using a hardcoded maximum row width of 8,192 pixels but converts JPEG pixel data using the server-supplied rectangle width without adequately checking that the output fits within the buffer. A malicious server can supply an oversized Tight JPEG rectangle that causes the conversion loop to write beyond the allocated memory. In an allocation demonstrated during testing, which included 256 bytes of padding, the out-of-bounds write began at a rectangle width of 8,257 pixels.

Exploitation requires a vulnerable viewer to establish a session with an attacker-controlled or compromised VNC server and process its crafted update. The server can advertise a sufficiently large framebuffer, so checking that the rectangle fits within the advertised framebuffer does not, by itself, prevent this overflow. Authentication or transport encryption does not prevent exploitation by a malicious server participating in the session.

Impact

An attacker controlling a VNC server can corrupt heap memory in a connected vulnerable viewer, terminating the application and interrupting the remote desktop session. Memory corruption may also permit arbitrary code execution with the privileges of the user running the viewer, but only denial of service was confirmed during testing.

Solution

Review the Vendor Information section for product-specific patch information.

According to UltraVNC’s release notes, the Tight JPEG heap overflow vulnerability was addressed in version 1.8.2.8. Users should upgrade to a current supported release containing that fix, such as version 1.8.3.1.

Unfortunately, we were unable to reach TightVNC to coordinate a fix for the affected 1.3.10 Windows viewer. Users should replace affected viewers with a maintained version or an alternative solution that has been confirmed to address the vulnerability.

Until a corrected viewer is deployed, restrict connections to trusted VNC servers only. This reduces exposure but does not protect against a compromised trusted server.

Acknowledgements

Thank you to re9rch for reporting this vulnerability. This document was written by Michael Bragg.

Overview

Multiple arbitrary file read and write vulnerabilities have been identified in applications that use ImageMagick with insufficiently restrictive security policies. Collectively referred to as ImageTragick2, these issues arise when ImageMagick processes attacker-controlled SVG or PostScript content using dangerous coders or delegates permitted by its default or application-supplied configuration. An attacker who can upload an image, or otherwise cause an application to process crafted image content, may be able to read or write files accessible to the ImageMagick process. In some deployments, these capabilities may be chained to achieve arbitrary code execution, compromising the confidentiality, integrity, and availability of the affected application and host.

Description

ImageMagick is a widely used open-source image-processing suite. Web and content-management applications, including Ruby on Rails, WordPress, MediaWiki, ownCloud Classic, and Redmine, may use ImageMagick for operations such as thumbnail generation, cropping, conversion, and transformation. ImageMagick is also commonly included in containerized AI image-processing pipelines. It may operate before inference to normalize or transform inputs, or after inference to convert and prepare generated output. In these environments, images may originate not only from direct uploads but also from URLs, automated agents, datasets, model outputs, or other upstream services.

Two vulnerability variants have been identified:
Coder invocation through SVG (MSL injection)

ImageMagick's SVG processing can allow a crafted SVG <image> element to invoke a dangerous coder through its xlink:href value, for example, by referencing an MSL: resource. ImageMagick may then interpret the referenced content as a Magick Scripting Language (MSL) script. The script can invoke additional image readers and direct attacker-controlled image data to selected filesystem paths, enabling unauthorized file access. Exploitation depends on the internal SVG coder and the required dangerous coders being available to the ImageMagick process.

Ghostscript invocation through content detection

ImageMagick's content-based format detection may identify crafted input as PostScript and invoke Ghostscript, a separate interpreter used by ImageMagick to handle PostScript, EPS, and PDF, even when the filename or declared type suggests another format. Although Ghostscript is invoked with -dSAFER, the observed configuration permits file access within /tmp. A crafted PostScript file may therefore read or write data in that directory. This can affect applications that use shared temporary storage for uploaded files, processing artifacts, sessions, or other security-sensitive data.

These issues highlight an important aspect of ImageMagick's security model: Behavior that can be restricted through a custom security policy is treated as a configuration issue, not a vulnerability in ImageMagick itself. Applications and distributions are therefore responsible for deploying a policy appropriate to their threat model. Many integrations, however, process untrusted content without a sufficiently restrictive policy.

Impact

An attacker who can cause an affected application to process crafted SVG or PostScript content may be able to read or write files in directory locations accessible to the ImageMagick process. In some cases, arbitrary code execution is possible when file access can be combined with writable executable content. AI-enabled services that utilize ImageMagick may face additional exposure because of untrusted image processing. In container deployments, writable host mounts, shared volumes, credentials, or inference artifacts can substantially increase the impact of a successful exploit.

Solution

Consult the Vendor Information section for product-specific updates and mitigations. Users of products that integrate ImageMagick, including Ruby on Rails, WordPress, MediaWiki, ownCloud Classic, and Redmine, should install vendor-provided updates when available. Updating ImageMagick alone may be insufficient if its security policy continues to permit dangerous coders or delegates.

Apply a custom policy.xml based on an allowlist: enable only the formats and operations the application requires, and disable unnecessary coders and delegates, including MSL, MVG, PS, EPS, and PDF. ImageMagick's bundled secure policy template may not be sufficient for every deployment; verify the effective policy and confirm that prohibited formats are rejected.

Additional recommendations include:
- Isolate image processing: Process untrusted images in a dedicated, minimally privileged environment with restricted filesystem access. Apply the same controls to AI preprocessing and post-processing pipelines.
- Validate and constrain input: Verify file content rather than relying on filenames, extensions, or client-supplied media types.
- Monitor processing activity: Alert on ImageMagick policy violations, unexpected delegate or coder use, unusual processing failures, and unexpected file creation.

Acknowledgements

Thanks to RyotaK of GMO Flatt Security Inc. for reporting these vulnerabilities. The pwn.ai team independently discovered Variant 2 and reported it to WordPress as CVE-2026-65640. This document was written by Vijay Sarvepalli and Molly Jaconski.

Overview

The npm library promzard, versions 4.0.0 and earlier, is vulnerable to remote code execution due to direct string interpolation of context object keys, which allows unsanitized JavaScript code injection.

Description

promzard is a Node.js library designed to automate configuration workflows by evaluating template modules and generating data objects via interactive prompting. The library allows users to provide a context object ctx to expose specific data to the template module.

promzard builds an object by walking the template module for prompt() and asynchronous functions. The keys of ctx, however, are treated as raw JavaScript source code instead of inert data. The implementation performs direct string interpolation of ctx keys, without validation or sanitization, into the parameter list of a function-expression source string that is then evaluated with vm.runInThisContext(). A key containing attacker-controlled JavaScript syntax can be executed during evaluation.

Impact

An attacker capable of influencing the ctx object’s keys (e.g. via parsed configuration file, an HTTP request, or environment variables) can break out of the function parameter list and inject arbitrary JavaScript code. This results in remote code execution within the context of the Node.js process.

Solution

Unfortunately, the maintainers of promzard could not be reached to coordinate the vulnerability. The CERT/CC recommends users ensure that any data used to populate ctx is strictly validated, and that arbitrary keys should not be passed from untrusted sources.

Acknowledgements

Thanks to Abdullah Hamdan for reporting this vulnerability. This document was written by Alex Lewis.

Overview

ComfyUI-Easy-Use version 1.4.1 and earlier contains a vulnerability in its save_preview() handler that allows an unauthenticated attacker to overwrite an installed custom node’s Python file. An attacker who can reach the affected ComfyUI instance over the network can use the overwrite to execute arbitrary code when ComfyUI restarts.

Description

ComfyUI is a node-based interface for building generative AI workflows. ComfyUI-Easy-Use is an extension that adds custom nodes and workflow utilities.
An attacker can upload a Python file to ComfyUI’s input directory then use save_preview() to copy that file over an installed custom node’s __init__.py. Upon restart, ComfyUI will import and execute the modified node. Remote exploitation requires a deployment that exposes the affected routes to the attacker without authentication.

Impact

An unauthenticated attacker who can reach the affected routes can execute arbitrary Python code and operating system commands with the privileges of the ComfyUI process. The attacker can read or modify models, workflows, and other files accessible to the process and obtain credentials available in its environment. Exploitation requires no user interaction. The reporter confirmed the vulnerability in ComfyUI-Easy-Use version up to verion 1.4.1.

Solution

Unfortunately, the maintainer of ComfyUI-Easy-Use could not be reached to coordinate this vulnerability. To mitigate the vulnerability, remove the extension or restrict network access to ComfyUI to trusted users. The maintainer have released a fix in main as commit 8a0f2fc412.

Acknowledgements

Thanks to Nguyen Huy Hoang for reporting this vulnerability. This document was written by Alex Lewis and Michael Bragg.

Az SAP novemberi havi biztonsági frissítési ciklusában négy, maximális, 10.0-s CVSS-pontszámmal értékelt sérülékenységet javított. Mind a négyet támadók bejelentkezés nélkül is kihasználhatják, ezért a SAP sürgős javítást javasol. Három hiba az SAP NetWeaver alkalmazásszerverben található, egy pedig a Web Dispatcherben, amely az internetről érkező webkéréseket fogadja és továbbítja az SAP-rendszerek felé. A hibák egy része […]

Lengyelország ideiglenesen leállította az ePUAP nevű országos kormányzati szolgáltatási platformot, miután a hatóságok észleltek és megállítottak egy kibertámadást.

A Maersk beismerte, hogy egy általa felvásárolt vállalat rendszereibe behatolt egy rosszindulatú szereplő, és adatokat lopott el.

Az ESET kutatói egy korábban nem dokumentált, Cereal nevű eszközkészletet azonosítottak, amelyet a Turla nevű, Oroszországhoz kötődő APT-csoport használ. A készlet Microsoft Exchange-levelezőszerverekre települ, onnan célzottan gyűjt ki leveleket. A támadóknak nincs külön vezérlőszervere, az áldozat saját, internetről elérhető Exchange-szervere szolgál a parancsok fogadására. A Turla, más néven Snake, legalább 2004 óta aktív, és az […]

Az iVerify jelentése szerint a kémprogramok alkalmazása egyre kevésbé korlátozódik a kiemelt személyek és állami célpontok elleni műveletekre, a kiberbűnözők egyre gyakrabban veszélyeztetik az átlagfelhasználók eszközeit is.

A Microsoft novemberi Patch Keddjén több mint ezer sérülékenységet hoztak nyilvánosságra, amelyek közül egyet már aktívan kihasználnak.

Az Adobe 2026. novemberi frissítőcsomagjában összesen 110 sebezhetőség került javításra, 9 különböző termékben, köztük az AEM, a Premiere, a Photoshop, az After Effects, a Connect, az Audition, a Dimension, a Content Credentials SDK és a Media Encoder szoftverekben.

Az ukrán hatóságok négy embert gyanúsítottak meg olyan csaló telefonos ügyfélszolgálati központokból álló hálózatok működtetésével, amelynek segítségével hamis kirptovaluta befektetéseken keresztül több millió eurót csaltak ki német állampolgároktól.

Az oroszbarát NoName057(16) hackercsoport európai politikusok, rendvédelmi vezetők és újságírók személyes adatait is közzétették a dark weben, illetve kriptovalutában fizetett jutalmat ajánlott fel azok számára, akik még további információt szolgáltatnak a célpontokról vagy azok családtagjairól.

A DigiCert, digitális tanúsítványokat kibocsátó hitelesítésszolgáltató vállalat, adatvédelmi incidenst jelentett be, amelynek során illetéktelenek fértek hozzá egy külső hálózatból elérhetővé vált belső üzleti rendszer adatbázisához.

Komoly kibertámadás érte a Müncheni Műszaki Egyetemet (TUM), amelynek során a támadók megszerezték a myTUM portálon regisztrált felhasználók központi belépési adatait.

Adatvédelmi incidens érte az Amplifon egészségügyi vállalatot, amely során amerikai ügyfelek személyes, pénzügyi és egészségügyi adatai kompromittálódtak. Az Amplifon először február 11-én észlelt gyanús tevékenységet rendszereiben. A későbbi vizsgálat megállapította, hogy a támadók január 18. és február 8. között férhettek hozzá a vállalat fájljaihoz. Az érintett adatok között nevek, vezetői engedélyek, személyazonosító okmányok, egészségügyi és […]

A Google hétfőn adta ki a Chrome legújabb biztonsági frissítését, amelyben 9 sebezhetőség, köztük egy, feltehetően aktívan kihasznált nulladik napi (zero day) hiba is javításra került.

A mesterséges intelligencia segítségével vállalatvezetők és ügyvédek személyazonosságával visszaélve közel 129 millió dollárt csalt ki egy nemzetközi bűnözői csoport az amerikai hatóságok szerint.

A francia kormány hivatalosan Iránt vádolja az ipari hűtő- és fagyasztóberendezések elleni kibertámadásokért.

Overview

Multiple vulnerabilities in the FrodoBots EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) may allow remote code execution, unauthorized access to onboard sensors, disclosure of sensitive information, and full compromise of affected devices. Exploitation may enable an attacker to remotely control the rover, access audiovisual streams, or pivot into the user’s network.

Description

The FrodoBots EarthRover Mini+ is a compact, internet‑connected mobile robot used in educational and consumer environments. The device includes a camera, microphone, motor controllers, and multiple onboard services. Multiple vulnerabilities in the EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) can allow remote code execution, unauthorized access to onboard sensors, exposure of sensitive data, and complete device compromise. An attacker could potentially take remote control of the rover, access its audio and video streams, or use it to gain a foothold in its network.

CVE-2026-121685: The firmware contains several sets of hard-coded, fleet‑wide credentials, including BasicAuth credentials for an Agora token service, AWS IAM (Amazon Web Services Identity and Access Management) access keys, Amazon Web Services Internet of Things Message Queuing Telemetry Transport (AWS IoT MQTT) credentials, and a Slack incoming webhook URL. Agora Token Service is an open source server that generates secure, time‑limited authentication tokens for use with Agora.io’s RTC (Real‑Time Communication) and RTM (Real‑Time Messaging) services. A Slack incoming webhook URL is a unique endpoint that lets external systems send messages into a Slack channel without the need for a full Slack application. These are embedded directly in frodobot.bin and are accessible through static analysis of the publicly downloadable firmware or from any device. Extraction requires no special privileges.

CVE-2026-121686: Unauthenticated remote command execution is allowed via Message Queuing Telemetry Transport (MQTT). A firmware method accepts arbitrary shell commands delivered via Amazon Web Services Internet of Things Message Queuing Telemetry Transport (AWS IoT MQTT) messages and executes them as root. Access is gated only by shared Internet of Things (IoT) credentials, with no per‑device authentication, enabling remote code execution (RCE) as root across the fleet. The IoT credentials are hard-coded in the firmware as discussed in CVE-2026-121685.

CVE-2026-121687: Several local interfaces are exposed without authentication. These services allow full local compromise of device functionality and provide access to sensitive information.
* HTTP REST API on port 80 (motor control, telemetry/GPS/IMEI) contains endpoints that reveal the plaintext Wi‑Fi password, enable Wi‑Fi join functionality, diagnostic export services
* Android Debug Bridge (ADB) root shell on port 5555
* SSH on port 22

CVE-2026-121688: The firmware contains an insecure STM32 update mechanism. STM32 is a family of 32-bit microcontrollers and is based primarily on Arm Cortex-M processor cores. They are widely used in embedded systems, IoT devices, industrial controls, robotics, automotive electronics, and consumer products. The STM32 motor‑controller firmware is fetched over unencrypted HTTP. Integrity is validated only via MD5, with the hash provided in the same unprotected response. No code‑signing mechanism is implemented, allowing firmware to be replaced with potentially malicious code.

CVE-2026-121689: The firmware exposes sensitive credentials through multiple insecure mechanisms. The Wi‑Fi PSK is stored in plaintext in wpa_supplicant.conf and is disclosed through unauthenticated API endpoints and diagnostic exports. Additionally, unauthenticated ADB access allows retrieval of the /etc/shadow file.

CVE-2026-121690: The firmware executes code with unnecessary privileges. All processes run as root and the system lacks privilege separation. The compromise of any single service results in full administrative control of the device.

Impact

Exploitation of these vulnerabilities may allow:
* Unauthorized access to live camera and microphone feeds.
* Fleet‑wide remote root access and full robot control via MQTT.
* Extraction of the user’s Wi‑Fi credentials and lateral movement onto the local network.
* Persistent compromise through tampered motor‑controller firmware.
* Unauthorized posting to the vendor’s Slack channels and potential exposure of backend infrastructure via IAM credential misuse.
* Given the rover’s mobility and sensor suite, exploitation may enable both digital and physical impacts.

Solution

As of this writing, the vendor has provided the following remediation status:

CVE-2026-121685 (Hard-coded credentials): Addressed

Most embedded credentials have been removed. One credential remains for requesting an Agora session token; backend authorization checks restrict misuse. Remaining credentials are limited to session‑bound operations.

CVE-2026-121686 (Remote command execution): Addressed

Arbitrary shell command execution has been removed. The device now supports only a small set of predefined management commands (e.g., reboot).

CVE-2026-121687 -- CVE-2026-121690. (Local interfaces and privilege model): Addressed or not remotely exploitable under current deployment model.

Local interfaces require connection to the device’s Wi‑Fi access point, which has a configurable password. The vendor asserts that an attacker must be physically near the device and connected to its Wi‑Fi network to exploit these interfaces. The firmware update process is manual and conducted through the local Wi‑Fi network.

The vendor validated changes via static analysis and internal implementation review, and considers the findings fixed, mitigated, or not applicable in the current deployment model.

Users are encouraged to update to the latest version of the FrodoBots EarthRover Mini+ firmware.

Acknowledgements

Thank you to Justin Davis for reporting these vulnerabilities. This document was written by Bob Kemerer.