Skip to content
OpenAdvisories
High WID-SEC-2026-2618 13 CVEs

IBM App Connect Enterprise: Mehrere Schwachstellen

Published Aug 2, 2026 · Updated Oct 4, 2026 · Revision 5 · de-DE

Summary

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Daten zu manipulieren.

Product

IBM App Connect Enterprise kombiniert die branchenbewährten Technologien des IBM Integration Bus mit Cloud-nativen Technologien.

Vulnerabilities 13

  • High 7.5

    undici WebSocket client vulnerable to denial of service via fragment count bypass

    Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that ea…

  • High 7.5

    fast-uri vulnerable to host confusion via failed IDN canonicalization

    fast-uri versions 2.3.1 through 3.1.2 and 4.0.0 fail to canonicalize Unicode (IDN) hostnames for HTTP-family URLs. The IDN conversion path calls a helper that does not exist on the global URL constructor, silently leaving the host in its original Unicode form…

  • High 7.5

    js-yaml: YAML merge-key chains can force quadratic CPU consumption

    js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the…

  • High 7.5

    undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse

    Impact: When using Socks5ProxyAgent, undici reuses a single connection pool across different origins without verifying that the pool's origin matches the requested origin. All requests are dispatched through the pool connected to the first origin, regardless …

  • High 7.5

    undici WebSocket client vulnerable to denial of service via cumulative fragment bypass

    Impact: The undici WebSocket client enforces maxPayloadSize per-frame but does not enforce the cumulative size of fragmented uncompressed messages. A malicious WebSocket server can stream many small fragments that each pass per-frame validation but collective…

  • High 7.4

    undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent

    Impact: undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert…

  • Medium 5.9

    undici vulnerable to cross-user information disclosure via shared cache whitespace bypass

    Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The p…

  • Medium 5.9

    undici vulnerable to HTTP header injection via Set-Cookie percent-decoding

    Impact: undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 §5.4 does not specify any decoding and browsers do not decode…

  • Medium 5.3

    js-yaml: Quadratic-complexity DoS in merge key handling via repeated aliases

    js-yaml is a JavaScript YAML parser and dumper. Prior to 4.2.0 and 3.15.0, a crafted YAML document can trigger algorithmic CPU exhaustion in js-yaml merge-key processing (<<) by repeating the same alias many times in a merge sequence. This causes quadratic pa…

  • Medium 5.3

    opentelemetry-js: Unbounded memory allocation in W3C Baggage propagation

    opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 …

  • Medium 5.3

    protobufjs: Denial of Service via infinite loop in .proto option parsing

    protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.5 and 8.6.6, protobufjs parsed option names by advancing through schema tokens until reaching an = token without checking for end of input, so a crafted .proto schema that o…

  • Low 3.7

    undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching

    Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the th…

  • Low 3.7

    undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse

    Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatch…

Revision history

  1. #5

    Neue Updates von IBM aufgenommen

  2. #4

    Neue Updates von Red Hat aufgenommen

  3. #3

    Neue Updates von Red Hat aufgenommen

  4. #2

    Neue Updates von Red Hat aufgenommen

  5. #1

    Initiale Fassung

References