Vulnerabilidades

*** Pendiente de traducción *** Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches<br /> additional certificates (extraCerts) sent in a CMP message, but never expunges<br /> them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX<br /> frequently, this cache of extraCerts may grow unboundedly, and a malicious<br /> client may flood a CMP server with requests driving this growth.<br /> <br /> Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX<br /> for the lifetime of a server process may observe unbounded memory growth in the<br /> event a malicious client repeatedly sends requests containing unique extra<br /> certificates, which may lead to OOM conditions.<br /> <br /> CWE: CWE-770: Allocation of Resources Without Limits or Throttling<br /> <br /> Description: If a remote user sends CMP messages to a server with a list of<br /> extraCerts and the message is rejected, the extraCerts from the message remains<br /> in the server contexts untrusted certificate stack. This exposes servers with<br /> long lived ctx objects to Denial of Service attacks in which an attacker sends<br /> messages intending to be rejected with a large list of additional certificates<br /> repeatedly, forcing the server to store them indefinitely.<br /> <br /> The issue was fixed by removing the added extra certs if the message is<br /> rejected, using the same method as when the context is configured to not do<br /> caching at all.<br /> <br /> FIPS impact: no<br /> As the CMP code lives outside the FIPS module boundary, no FIPS<br /> modules are affected by this CVE.

*** Pendiente de traducción *** Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly<br /> sends ack-eliciting packets while not acknowledging ACK-only responses, the<br /> QUIC stack can retain ACK-only packet metadata for the lifetime of the<br /> connection.<br /> <br /> Impact summary: A remote peer that can complete a QUIC handshake can<br /> cause connection-scoped memory growth which may lead to Denial of Service<br /> through memory exhaustion, especially with sustained traffic or many concurrent<br /> QUIC connections.<br /> <br /> CWE: CWE-770: Allocation of Resources Without Limits or Throttling<br /> <br /> Description: When the OpenSSL QUIC stack sends an ACK-only packet,<br /> there is no requirement by the QUIC protocol that the peer will acknowledge<br /> that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL<br /> implementation stores the metadata about the ACK frames regardless.<br /> In and of itself that&amp;#39;s ok, but if a malicious peer establishes a connection, and<br /> then drives the connection such that ACK-only packets are forced from the <br /> OpenSSL implementation peer (i.e., by sending numerous PING frames),<br /> and then withholding any subsequent acks for ack-eliciting data, like<br /> legitimate data, said malicious peer can force inappropriate memory growth<br /> on the OpenSSL peer, potentially leading to a Denial of Service.<br /> <br /> The fix is to ensure that we account for the transmission of the ACK-only<br /> packet in the packet histories high and low watermark without actually storing<br /> the ACK-only packet metadata itself.<br /> <br /> FIPS impact: no<br /> The OpenSSL FIPS module is not affected as the QUIC code is<br /> outside the FIPS module boundary.

*** Pendiente de traducción *** Issue summary: OpenSSL CMP password based protection verification only<br /> checks whether the protectionAlg parameter was not NULL and not its<br /> ASN.1 type, before treating it as a PBMParameter. A crafted message can<br /> contain a parameter of a different type, which is then dereferenced as an<br /> invalid pointer.<br /> <br /> Impact summary: A remote, unauthenticated attacker can crash an application<br /> acting as a CMP server that accepts PBM-protected messages, or a CMP client<br /> talking to a malicious or intercepted CMP server, resulting in a Denial of<br /> Service.<br /> <br /> CWE: CWE-476: NULL Pointer Dereference<br /> <br /> Description: When verifying the password-based MAC protection of a CMP<br /> message, OpenSSL library reads the protectionAlg algorithm parameter with<br /> X509_ALGOR_get0(), which returns both the parameter type and its value<br /> pointer. The value is then cast to an ASN1_STRING and treated as the<br /> expected PBMParameter after only checking that pointer is not NULL. The<br /> parameter type returned by X509_ALGOR_get0() was never consulted.<br /> <br /> This happens during protection verification, before any MAC is computed, so<br /> no knowledge of the PBM shared secret is required; the only precondition is<br /> that PBM verification is reachable. On the server side this is reached from<br /> OSSL_CMP_SRV_process_request() for any application that stands up a CMP<br /> server accepting PBM-protected messages, and on the client side from CMP<br /> response validation against a malicious or on-path (MITM) server. The<br /> reliable consequence is a denial of service; there is no memory disclosure,<br /> no controlled memory write, and no path to code execution. CMP is a<br /> specialized feature that an application must explicitly enable.<br /> <br /> FIPS impact: no<br /> As the CMP code lives outside the FIPS module boundary, no FIPS modules<br /> are affected by this CVE.

*** 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: In a server or client configuration with RFC7250 Raw Public Keys (RPKs)<br /> enabled, and only the private key (with no associated certificate) configured locally,<br /> a NULL pointer dereference may occur when the remote peer solicits raw public keys and<br /> also sends the typically omitted "signature_algorithms_cert" TLS extension.<br /> <br /> Impact summary: The impact is limited to a possible Denial of Service as a result of<br /> an application abort, no data disclosure or remote command execution are possible.<br /> <br /> CWE: CWE-476: NULL Pointer Dereference<br /> <br /> Description: While a passing comment in sample code in the documentation suggests<br /> that key-only RPK configurations are supported, the best-practice RPK configuration<br /> is to always configure a corresponding certificate (possibly self-signed or<br /> signed by any convenient CA).<br /> <br /> When the private key is configured along with a matching certificate, the<br /> "signature_algorithms_cert" extension is handled reliably even without the<br /> fix, and peer clients or servers that don&amp;#39;t support raw public keys may be<br /> able to complete a TLS connection by pinning or verifying the corresponding<br /> certificate or its public key.<br /> <br /> Deployments that prefer to configure just a private key with no certificate<br /> need to upgrade to an updated release as noted below.<br /> <br /> FIPS impact: no<br /> <br /> No FIPS modules are affected by this issue, as the SSL protocol implementation<br /> is outside the OpenSSL FIPS module boundary.

*** 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 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.4.3 fails to enforce scope-based authorization on nine comment panel admin endpoints, allowing access tokens with minimal scopes to perform full comment moderation operations. Attackers with a limited-scope access token can list, approve, reject, delete comments, and modify comment system settings by directly accessing the unprotected panel endpoints.

*** 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.