Vulnerabilidades

*** Pendiente de traducción *** Issue summary: Receiving a DTLS record for a future epoch while a handshake<br /> is in progress causes OpenSSL to buffer far more memory than the record<br /> itself requires.<br /> <br /> Impact summary: A peer can use a small amount of network traffic to make an<br /> OpenSSL DTLS endpoint retain a disproportionately large amount of memory,<br /> which may lead to a Denial of Service.<br /> <br /> CWE: CWE-405: Asymmetric Resource Consumption (Amplification)<br /> <br /> Description: While a DTLS handshake is in progress, a peer may legitimately<br /> have already moved on to the next epoch (for example, having sent its<br /> ChangeCipherSpec and Finished messages) before the local endpoint has<br /> processed the same transition, typically because of reordering on the<br /> underlying UDP transport. OpenSSL buffers such early records so that they<br /> can be processed once the local endpoint catches up.<br /> <br /> Buffering a record currently retains the entire read buffer it arrived in,<br /> which is sized to hold the largest possible DTLS record (around 16<br /> kilobytes), rather than just the bytes that make up the record itself. Up<br /> to 100 such records may be buffered per connection. As a result, a peer<br /> that sends a stream of small forged records claiming to belong to the next<br /> epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of<br /> memory, despite sending only a small fraction of that amount of data over<br /> the network.<br /> <br /> An attacker therefore gains a memory amplification factor of around 1200,<br /> and can multiply the effect across as many associations as it is able to<br /> open, making this a remote memory exhaustion Denial of Service risk for<br /> DTLS servers. Since the memory retained per connection remains bounded,<br /> and any limit an application already places on the number of concurrent<br /> associations also bounds the total exposure, this issue has been assessed<br /> as Low severity.<br /> <br /> FIPS impact: no<br /> <br /> No FIPS modules are affected by this issue as the affected code is outside<br /> the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this<br /> issue.<br /> <br /> OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2.<br /> OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4.<br /> OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8.<br /> OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7.<br /> OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.<br /> <br /> Premium support customers only:<br /> OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi<br /> OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr<br /> <br /> This issue was reported on 18 May 2026 by Amazon Web Services.<br /> The fix has been developed by Matt Caswell.<br /> <br /> -- cut (non-publishing metadata for internal use) --<br /> Reported by: Amazon Web Services<br /> Fixed by: Matt Caswell

*** Pendiente de traducción *** Crater Invoice through 6.0.6 contains a path traversal vulnerability in the self-update API that allows authenticated company owners to write arbitrary files outside the intended extraction directory by supplying crafted ZIP archives with ../ sequences to the unzip endpoint. Attackers can exploit unsanitized ZIP entry names passed to PHP&amp;#39;s ZipArchive::extractTo() to write arbitrary PHP files into the web-accessible public directory and achieve remote code execution on the server.

*** Pendiente de traducción *** Issue summary: QUIC server may double free QRX (QUIC record layer RX) object<br /> when channel creation fails for initial packet.<br /> <br /> Impact summary: Double free leads to heap corruption, which typically results in <br /> termination of QUIC server process, leading to Denial of Service. There is so<br /> far no evidence that this double free is exploitable for remote code execution,<br /> thus it is considered highly improbable.<br /> <br /> CWE: CWE-415: Double Free<br /> <br /> Description: In order to validate initial packet, OpenSSL QUIC stack default<br /> packet handler (port_default_packet_handler()) creates a so-called QRX object.<br /> If the initial packet validates successfully with QRX object, the default packet<br /> handler proceeds to channel (connection object) creation. The QRX object used<br /> for packet validation is passed to port_bind_channel(), so it becomes part of<br /> the newly created connection. If port_bind_channel() fails, then it also frees<br /> the QRX object. Once port_bind_channel() returns, the port_default_packet_handler()<br /> detects the failure and proceeds to the error branch, where the same QRX object is<br /> freed for the second time.<br /> <br /> The failure in port_bind_channel() function can be induced with a relatively<br /> low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet<br /> carries DCID (destination connection ID) which is shorter than 8 bytes, then<br /> port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid()<br /> detects that the DCID has invalid length.<br /> <br /> FIPS impact: no<br /> The FIPS module is not affected, as the QUIC implementation is outside of<br /> the OpenSSL FIPS module boundary.

*** Pendiente de traducción *** Ech0 before 4.4.3 contains a stored cross-site scripting vulnerability in the file upload endpoint that validates Content-Type using only client-supplied headers without server-side inspection. Attackers with admin privileges can upload SVG or HTML files containing JavaScript that executes in the application origin when accessed by any user, enabling session hijacking and data exfiltration.

*** Pendiente de traducción *** Ech0 through 4.2.1 contains a server-side request forgery vulnerability in the validateWebhookURL function (webhook_setting_service.go), which only validates literal IP addresses via net.ParseIP() and fails to reject hostnames that DNS-resolve to private or internal IPs (e.g., 169.254.169.254.nip.io). An attacker with admin privileges can create a webhook with such a hostname to bypass validation and cause the server to make requests to internal services, cloud metadata endpoints, and private network resources. The issue is fixed in 4.4.3.

*** Pendiente de traducción *** Ech0 before 4.4.3 protects the PUT /user endpoint with the profile:read scope, a read-only scope, but allows write operations including password changes. An attacker with an admin&amp;#39;s profile:read access token can change the admin&amp;#39;s password and login to obtain an unrestricted session token that bypasses all scope enforcement.

*** Pendiente de traducción *** Ech0 before 4.4.3 lacks authorization checks on system log endpoints allowing any authenticated non-admin user to read and stream all server logs. Attackers can access historical logs and real-time log streams via GET /api/system/logs, GET /api/system/logs/stream, and WS /ws/system/logs to gather reconnaissance data including internal file paths, error stack traces, and application state.

*** Pendiente de traducción *** Ech0 before 4.5.1 contains an authorization bypass vulnerability where session tokens skip scope validation in RequireScopes middleware, allowing logged-in non-admin users to access admin endpoints. Attackers can read system logs, visitor statistics, user emails, and subscribe to live WebSocket logs by sending authenticated session tokens to unprotected endpoints.

*** Pendiente de traducción *** Ech0 before 4.4.3 fails to enforce administrator authorization on dashboard log endpoints, allowing any authenticated user to access system logs. Attackers with valid user sessions can query GET /api/system/logs and subscribe to SSE and WebSocket log streams to retrieve sensitive operational data including file paths, stack traces, and internal URLs.

*** Pendiente de traducción *** Ech0 before 4.7.3 contains an authentication bypass vulnerability in the PUT /api/echo/like/:id endpoint that allows unauthenticated attackers to increment engagement metrics without identity verification or rate limiting. Attackers can send repeated requests to arbitrarily inflate the fav_count field for any known echo identifier, compromising the integrity of engagement metrics and social ranking systems.

*** Pendiente de traducción *** Ech0 before 4.7.3 fails to properly revoke access tokens created with never-expire option, allowing attackers to maintain perpetual authenticated access after token theft. Three independent revocation mechanisms fail: logout panics on nil ExpiresAt field, RevokeToken skips when remainTTL is zero, and admin delete does not blacklist the JTI, leaving stolen tokens cryptographically valid until JWT secret rotation.

*** Pendiente de traducción *** Ech0 before 4.7.3 contains a stored cross-site scripting vulnerability in the public RSS feed where tag names and markdown content are rendered without HTML escaping. Attackers with admin privileges can inject malicious tag names or raw HTML in echo content that executes as JavaScript in RSS readers that render HTML-type summaries, affecting anonymous subscribers and other users.