Skip to content
Fencer Vulns
critical 9.8

CVE-1999-1588 in the critical feed json

Buffer overflow in nlps_server in Sun Solaris x86 2.4, 2.5, and 2.5.1 allows remote attackers to execute arbitrary code as root via a long…

published 1999-12-31 26 y ago modified 2026-06-16 4 mo ago also EUVD-1999-1569

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
10.1%
EPSS 10.1% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Buffer overflow in nlps_server in Sun Solaris x86 2.4, 2.5, and 2.5.1 allows remote attackers to execute arbitrary code as root via a long string beginning with "NLPS:002:002:" to the listen (aka System V listener) port, TCP port 2766.

Timeline

  1. First public exploit (EDB-20602)
  2. Published

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2 y ago

Exploit prediction

10.08% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-20602 Solaris x86 2.4/2.5 - nlps_server Buffer Overflow remote, 1998-04-01
  • securityfocus.com http://www.securityfocus.com/data/vulnerabilities/exploits/nlps_server.c referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/2319 referenced PoC, tagged "exploit" by a source, unverified
  • security-protocols.com http://security-protocols.com/sploits/unsorted_exploits/nlps_server.c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • sun solaris

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.