CVE-1999-1450
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in (1) rlogin daemon rshd and (2) scheme on SCO UNIX OpenServer 5.0.5 and earlier, and SCO UnixWare 7.0.1 and earlier, allows remote attackers to gain privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRemote code execution vulnerability in the rlogin daemon (rshd) and related scheme on SCO UNIX OpenServer 5.0.5 and earlier and UnixWare 7.0.1 and earlier allows remote attackers to gain elevated privileges via the network service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.0.5= 5.0= 5.0.2= 5.0.4<= 2.1.3<= 7.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the SCO operating system versionRun 'uname -a' or 'cat /etc/*release*' or check /var/adm/syslog to determine the exact SCO OpenServer or UnixWare versionAffected if The system is running SCO OpenServer 5.0.5 or earlier, or UnixWare 7.0.1 or earlier
-
Determine if rlogin/rshd services are installedCheck for the presence of rlogind or rshd binaries: look in /usr/sbin/rlogind, /usr/sbin/rshd, or run 'ls -la /etc/inetd.conf' to see if these services are configuredAffected if The rlogind or rshd binaries exist on the system and are configured in inetd.conf
-
Verify if the rlogin service is currently activeCheck inetd configuration or running processes: 'ps -ef | grep rlogind' or 'ps -ef | grep rshd' or inspect /etc/inetd.conf for uncommented rlogin/rshd entriesAffected if The rlogin or rshd daemon is running or enabled in inetd configuration
-
Check network listening status for rlogin portsRun 'netstat -an | grep 513' or 'grep 513 /etc/services' to check if port 513 (rlogin) is listeningAffected if Port 513 or the rlogin service is bound to a network interface
A user is affected if they run a vulnerable SCO OpenServer or UnixWare version AND have the rlogin/rshd service enabled and accessible on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or remove the rlogin/rshd services immediately; migrate to secure alternatives like SSH; if these legacy SCO systems cannot be retired, isolate them behind a firewall with no external network access.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-1450 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data