Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-1150: Livingston Portmaster routers running ComOS use the same initial sequence number (ISN) for TCP conne

0
High
VulnerabilityCVE-1999-1150cve-1999-1150
Published: Tue Jun 30 1998 (06/30/1998, 04:00:00 UTC)
Source: NVD
Vendor/Project: livingston_portmaster
Product: portmaster

Description

Livingston Portmaster routers running ComOS use the same initial sequence number (ISN) for TCP connections, which allows remote attackers to conduct spoofing and hijack TCP sessions.

AI-Powered Analysis

AILast updated: 06/29/2025, 20:55:58 UTC

Technical Analysis

CVE-1999-1150 is a vulnerability affecting Livingston Portmaster routers running the ComOS operating system. The core issue lies in the use of a static or predictable Initial Sequence Number (ISN) for TCP connections. Normally, TCP connections use randomized ISNs to prevent attackers from predicting the sequence numbers used in a session. However, in this case, the Portmaster routers use the same ISN for all TCP connections, which significantly weakens the security of the TCP session establishment process. This flaw enables remote attackers to perform TCP session hijacking and spoofing attacks by predicting or knowing the sequence numbers, allowing them to inject malicious packets into an existing TCP session or impersonate a trusted host. The vulnerability does not require authentication and can be exploited remotely over the network. The CVSS v2 base score is 7.5, indicating a high severity level, with the vector AV:N/AC:L/Au:N/C:P/I:P/A:P meaning the attack can be performed remotely with low complexity, no authentication, and impacts confidentiality, integrity, and availability. There is no patch available for this vulnerability, and no known exploits have been reported in the wild. Given the age of this vulnerability (published in 1998) and the specific product affected, it is likely that many affected devices are legacy systems still in operation in some environments. The vulnerability fundamentally undermines the trustworthiness of TCP sessions passing through these routers, potentially allowing attackers to intercept, modify, or disrupt network communications.

Potential Impact

For European organizations, the impact of this vulnerability can be significant if Livingston Portmaster routers running ComOS are still deployed within their network infrastructure. Exploitation could lead to unauthorized access to sensitive data, session hijacking, and disruption of critical network services. This could affect confidentiality by exposing data in transit, integrity by allowing attackers to alter communications, and availability by disrupting legitimate sessions. Industries with high reliance on secure network communications, such as finance, government, and critical infrastructure, would be particularly at risk. Additionally, the lack of available patches means organizations must rely on compensating controls or device replacement to mitigate the risk. The vulnerability could also be leveraged in targeted attacks against legacy systems that have not been updated or replaced, potentially leading to data breaches or operational disruptions.

Mitigation Recommendations

Since no patch is available for this vulnerability, European organizations should consider the following specific mitigation strategies: 1) Identify and inventory all Livingston Portmaster routers running ComOS within the network to assess exposure. 2) Replace affected routers with modern, supported devices that implement proper TCP ISN randomization and have ongoing security support. 3) If immediate replacement is not feasible, isolate affected routers in network segments with strict access controls and monitoring to limit exposure to untrusted networks. 4) Implement network-level protections such as ingress and egress filtering to prevent spoofed packets from entering or leaving the network. 5) Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous TCP sequence number behavior or session hijacking attempts. 6) Use VPNs or encrypted tunnels to protect sensitive communications traversing vulnerable routers, reducing the risk of interception or tampering. 7) Regularly monitor network traffic for signs of session hijacking or spoofing attacks. 8) Educate network administrators about the risks associated with legacy devices and the importance of timely hardware upgrades.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32bb6fd31d6ed7dea0d

Added to database: 5/20/2025, 3:43:39 PM

Last enriched: 6/29/2025, 8:55:58 PM

Last updated: 2/7/2026, 2:45:14 AM

Views: 36

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats