Amit Klein

**Name of the Vulnerable Software and Affected Versions** gVisor (affected versions not specified) **Description** A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP address and a per-boot identifier that could aid in tracking of a device in certain circumstances. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Fuchsia (affected versions not specified) **Description** The issue concerns vulnerabilities in the algorithms used by Fuchsia to populate network protocol header fields. Specifically, the vulnerabilities affect the TCP Initial Sequence Number (ISN), TCP timestamp, TCP and UDP source ports, and IPv4/IPv6 fragment ID. These vulnerabilities allow for the values to be guessed under certain circumstances. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** gVisor (affected versions not specified) **Description** The issue concerns weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor. This allowed an external attacker to predict these values in certain circumstances. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** macOS Sonoma versions prior to 14.5 iOS versions prior to 16.7.8 iPadOS versions prior to 16.7.8 macOS Ventura versions prior to 13.6.7 watchOS versions prior to 10.5 visionOS versions prior to 1.3 tvOS versions prior to 17.5 iOS versions prior to 17.5 iPadOS versions prior to 17.5 macOS Monterey versions prior to 12.7.5 **Description** A race condition was addressed with improved locking. An attacker in a privileged network position may be able to spoof network packets. **Recommendations** For macOS Sonoma versions prior to 14.5, update to macOS Sonoma 14.5. For iOS versions prior to 16.7.8, update to iOS 16.7.8. For iPadOS versions prior to 16.7.8, update to iPadOS 16.7.8. For macOS Ventura versions prior to 13.6.7, update to macOS Ventura 13.6.7. For watchOS versions prior to 10.5, update to watchOS 10.5. For visionOS versions prior to 1.3, update to visionOS 1.3. For tvOS versions prior to 17.5, update to tvOS 17.5. For iOS versions prior to 17.5, update to iOS 17.5. For iPadOS versions prior to 17.5, update to iPadOS 17.5. For macOS Monterey versions prior to 12.7.5, update to macOS Monterey 12.7.5.

**Name of the Vulnerable Software and Affected Versions** FileZilla Server versions up to 0.9.50 **Description** A problematic vulnerability was found in the PORT Handler component of FileZilla Server, allowing for remote attacks that lead to unintended intermediary. The issue can be addressed by upgrading to version 0.9.51. **Recommendations** For versions up to 0.9.50, upgrade to version 0.9.51 to address the issue.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 5.17.9 **Description** The issue is related to insufficient entropy in the Linux kernel, allowing a remote attacker to identify clients by determining the original source ports used by the TCP server. This is due to the use of Algorithm 4, also known as the Double-Hash Port Selection Algorithm, as defined in RFC 6056. **Recommendations** For Linux kernel versions prior to 5.17.9, update to version 5.17.9 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a memory leak problem in the TCP source port generation algorithm, which may allow an attacker to leak information and potentially cause a denial of service problem. This is due to the small table perturb size in the net/ipv4/tcp.c component. The exploitation of this issue may enable a remote attacker to predict the number of an outgoing TCP connection port. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: NetBSD versions prior to 9.3 Description: The issue concerns the IPv4 ID generation algorithm, which does not utilize appropriate cryptographic measures. Recommendations: For NetBSD versions prior to 9.3, update to version 9.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: NetBSD versions prior to 9.3 Description: The issue concerns a weak cryptographic PRNG used in the IPv6 Flow Label generation algorithm. Recommendations: For NetBSD versions prior to 9.3, update to version 9.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: NetBSD versions prior to 9.3 Description: The issue is related to an information leak in the TCP ISN (ISS) generation algorithm. This leak may potentially allow attackers to gather sensitive information. Recommendations: For versions prior to 9.3, update to version 9.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: NetBSD versions prior to 9.3 Description: The issue concerns a weak cryptographic PRNG used in the IPv6 fragment ID generation algorithm. Recommendations: For NetBSD versions prior to 9.3, update to version 9.3 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Squid versions prior to 4.13 Squid versions 5.x prior to 5.0.4 Description: The issue is related to inconsistent interpretation of HTTP requests, which can lead to HTTP Request Smuggling attacks against HTTP and HTTPS traffic, resulting in cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the proxy cache and any downstream caches with content from an arbitrary source. When configured for relaxed header parsing, Squid relays headers containing whitespace characters to upstream servers, which can be used to ignore the frame length specified in a Content-Length header. Recommendations: For Squid versions prior to 4.13, update to version 4.13 or later to resolve the issue. For Squid versions 5.x prior to 5.0.4, update to version 5.0.4 or later to resolve the issue. As a temporary workaround, consider disabling relaxed header parsing to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Squid versions prior to 4.12 Squid versions 5.x prior to 5.0.3 **Description** An issue in the http/ContentLengthInterpreter.cc component of Squid allows for a Request Smuggling and Poisoning attack against the HTTP cache. This can be achieved by sending an HTTP request with a Content-Length header containing specific characters, such as "+-" or uncommon shell whitespace character prefixes to the length field-value. The attack can be exploited by a remote attacker to poison the cache content using a specially crafted HTTP(S) request. **Recommendations** For Squid versions prior to 4.12, update to version 4.12 or later to resolve the issue. For Squid versions 5.x prior to 5.0.3, update to version 5.0.3 or later to resolve the issue. As a temporary workaround, consider restricting access to the http/ContentLengthInterpreter.cc component until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Windows TCP/IP (affected versions not specified) **Description** The issue is related to an information disclosure problem in the Windows TCP/IP stack, specifically with how it handles IPv6 flowlabel filled packets. This could allow a remote attacker to gain unauthorized access to protected information by using a specially crafted IPv6 packet. The vulnerability may enable attackers to obtain sensitive information and impact the system. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Linux kernel versions 4.3 through 5.x before 5.3.10 Description: The issue is related to the flow dissector feature in the Linux kernel, which has a device tracking vulnerability. This occurs because the auto flowlabel of a UDP IPv6 packet relies on a 32-bit hashrnd value as a secret, and jhash is used instead of siphash. The hashrnd value remains the same starting from boot time and can be inferred by an attacker, affecting net/core/flow dissector.c and related code. The vulnerability may allow a remote attacker to gain unauthorized access to protected information. Additionally, there is a possible packet injection due to improperly used crypto in the flow hash from keys function of flow dissector.c, which could lead to remote escalation of privilege with no additional execution privileges needed. Recommendations: For Linux kernel versions 4.3 through 5.x before 5.3.10, update to version 5.3.10 or later to resolve the issue. As a temporary workaround, consider restricting access to the flow dissector feature until a patch is available. Avoid using the `hashrnd` value in the affected code until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Node.js versions 0.10.x before 0.10.42 Node.js versions 0.11.6 through 0.11.16 Node.js versions 0.12.x before 0.12.10 Node.js versions 4.x before 4.3.0 Node.js versions 5.x before 5.6.0 **Description** The issue allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header. This can be demonstrated by using characters such as %c4%8d%c4%8a. **Recommendations** For Node.js versions 0.10.x before 0.10.42, update to version 0.10.42 or later. For Node.js versions 0.11.6 through 0.11.16, update to a version outside of this range, such as version 0.11.17 or later. For Node.js versions 0.12.x before 0.12.10, update to version 0.12.10 or later. For Node.js versions 4.x before 4.3.0, update to version 4.3.0 or later. For Node.js versions 5.x before 5.6.0, update to version 5.6.0 or later.

**Name of the Vulnerable Software and Affected Versions** Apple iOS versions prior to 9 **Description** The issue is related to errors in the code of the CFNetwork FTPProtocol component. It allows remote FTP proxy servers to trigger TCP connection attempts to intranet hosts via crafted responses. This can be exploited by a remote attacker to initiate TCP connections with nodes on the internal network using specially formed response requests. **Recommendations** For versions prior to 9, update to iOS version 9 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Apple Safari (affected versions not specified) Description: The JavaScript implementation in WebKit, used by Apple Safari, utilizes a weak random number generation algorithm. This weakness simplifies the task for remote attackers to track users by predicting the generated values. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Mozilla Firefox versions 3.5.10 through 3.5.11 Mozilla Firefox versions 3.6.4 through 3.6.8 Mozilla Firefox version 4.0 Beta1 **Description** The issue is related to the Math.random function in the JavaScript implementation, which uses a random number generator seeded only once per document object. This makes it easier for remote attackers to track a user or trick a user into acting upon a spoofed pop-up message by calculating the seed value. The issue is related to a "temporary footprint" and an "in-session phishing attack." **Recommendations** For Mozilla Firefox versions 3.5.10 through 3.5.11, update to a version that correctly fixes the random number generator seeding issue. For Mozilla Firefox versions 3.6.4 through 3.6.8, update to a version that correctly fixes the random number generator seeding issue. For Mozilla Firefox version 4.0 Beta1, update to a version that correctly fixes the random number generator seeding issue.

**Name of the Vulnerable Software and Affected Versions** Mozilla Firefox versions 3.5.10 through 3.5.11 Mozilla Firefox versions 3.6.4 through 3.6.8 Mozilla Firefox version 4.0 Beta1 **Description** The issue concerns the js InitRandom function in the JavaScript implementation, which uses a context pointer in conjunction with its successor pointer for seeding a random number generator. This makes it easier for remote attackers to guess the seed value via a brute-force attack. **Recommendations** For Mozilla Firefox versions 3.5.10 through 3.5.11, update to a version that fixes this issue. For Mozilla Firefox versions 3.6.4 through 3.6.8, update to a version that fixes this issue. For Mozilla Firefox version 4.0 Beta1, update to a version that fixes this issue.