CVE-2024-4741
HighSummary
Podatność dotyczy funkcji API OpenSSL SSL_free_buffers, która może prowadzić do dostępu do pamięci, która została wcześniej zwolniona w niektórych sytuacjach. Problem ten występuje tylko w aplikacjach, które bezpośrednio wywołują tę funkcję, co jest rzadkie.
Risk Assessment
Wykorzystanie tej podatności może prowadzić do uszkodzenia danych, awarii aplikacji lub wykonania dowolnego kodu. Organizacje powinny być świadome, że tylko nieliczne aplikacje są narażone na ten problem.
Recommendation
Zaleca się, aby administratorzy IT zidentyfikowali aplikacje korzystające z funkcji SSL_free_buffers i przeanalizowali ich kod w celu eliminacji potencjalnych zagrożeń. W przypadku wykrycia podatnych aplikacji, należy rozważyć ich aktualizację lub zastosowanie alternatywnych rozwiązań.
Related vulnerabilities
- CVE-2026-105105Critical
Missing authentication for critical function in the ait-server telemetry and command broker in NASA-AMMOS AIT-Core through 3.1.1. An unauthenticated remote attacker with network access to the ZeroMQ message bus can inject spacecraft command data, exfiltrate command and telemetry traffic, inject forged telemetry, or disrupt the bus. The ZeroMQ broker binds XSUB and XPUB sockets to all interfaces by default without authentication.
- CVE-2026-71885Critical
In Bouncy Castle for Java before 1.86, the Messaging Layer Security (MLS, RFC 9420) implementation did not bind an X.509 credential to a LeafNode's signature_key. LeafNode.verify() checked a leaf's signature against the signature_key carried in the leaf itself, while the credential's X.509 certificate chain was stored but never parsed or validated, so the end-entity certificate's public key was never required to match signature_key as RFC 9420 sec. 5.3 requires. An attacker could present another party's certificate as its credential while signing the leaf, and the enclosing KeyPackage, with an unrelated key, and be accepted under that other party's identity through KeyPackage.verify() and the Group leaf-validation path.
- CVE-2026-92084Critical
The Beaver Builder Page Builder plugin for WordPress up to version 2.11.0.5 is vulnerable to arbitrary shortcode execution. This is due to insufficient validation before running do_shortcode, allowing unauthenticated attackers to execute arbitrary shortcodes. Exploitation requires a page with the Sidebar module containing a widget that displays attacker-controlled text, such as the Recent Comments widget with approved comments.
- CVE-2026-87115Critical
The VikAppointments Services Booking Calendar plugin for WordPress up to version 1.2.21 is vulnerable to arbitrary file deletion due to insufficient file path validation in the extract function. This allows unauthenticated attackers to delete arbitrary files on the server, potentially leading to remote code execution (e.g., by deleting wp-config.php). Exploitation requires at least one File-type custom field published on the confirmation page.
- CVE-2026-105080Critical
In ConvertX before 0.19.0, converters/calibre.ts does not block recipe files and passes them to the ebook-convert program from Calibre. This allows executable code in .recipe or .downloaded_recipe files.
- CVE-2026-84411Critical
The web management service in affected RouterOS versions contains an integer underflow in HTTP request body handling that is reachable before authentication. An unauthenticated network attacker can exploit a single crafted request to achieve remote code execution as root or cause a denial of service.
- CVE-2026-95102Critical
WebSocket endpoints lack proper authentication mechanisms, enabling attackers to impersonate charging stations. By exploiting this weakness, attackers can gain unauthorized access to sensitive data or perform unauthorized actions. Since no authentication is required, this can lead to privilege escalation and potentially compromise the security of the entire system.
- CVE-2026-82042Critical
UTMStack before 11.2.16 contains an authentication bypass vulnerability that allows remote attackers to gain full administrative API access by presenting a valid Utm-Internal-Key header matching the INTERNAL_KEY environment variable value. The InternalApiKeyFilter accepts this key for any endpoint without path restriction, constant-time comparison, rate limiting, or audit logging. Attackers who obtain the key value can authenticate without a user account or JWT to create accounts, manage users, exfiltrate data, and modify security rules.
- CVE-2026-82041Critical
UTMStack before 11.2.16 contains a missing authorization vulnerability in UTMIncidentCommandWebsocket.processCommand(), the handler mapped to the /command/{hostname} STOMP destination, where no role check or command allowlist is applied before forwarding supplied commands. Any authenticated user, regardless of role, can send arbitrary operating-system commands over gRPC to any connected agent, resulting in command execution on monitored endpoints where agent processes commonly run as root or SYSTEM.
- CVE-2026-75937Critical
A specially crafted HTTP POST request to the web administration interface allows an unauthenticated attacker to execute arbitrary operating system commands with root privileges on the affected device. Disabling the web server when not configuring the device is recommended.
Original NVD description (English source)
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrive
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

