LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0568: rpc.admind in Solaris is not running in a secure mode.

rpc.admind in Solaris is not running in a secure mode.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This entry flags an insecure configuration in older Sun Solaris systems where the rpc.admind remote administration service runs without secure mode enabled. In that state, the service does not require strong authentication, meaning an attacker on the network could issue administrative commands as if they were a trusted operator. It is a legacy hardening issue rather than a modern software bug.

Executive priority

Low priority for most modern enterprises. Treat as a legacy hygiene item: relevant only if Solaris with Solstice AdminSuite remains in production. If such systems exist, prioritize based on their business criticality and network reachability rather than the CVE age.

Technical view

CVE-1999-0568 documents Solaris systems running rpc.admind (the Solstice AdminSuite daemon) without secure mode. In its default weak mode, rpc.admind relies on host-based trust rather than cryptographic authentication, allowing spoofed RPC requests to invoke privileged administrative actions. The public record contains no CVSS score, no CWE mapping, and no affected-version list. It is cataloged as a configuration weakness against legacy Solaris deployments, not a patchable code defect.

Likely exposure

Exposure is limited to organizations still operating legacy Sun Solaris hosts with Solstice AdminSuite and rpc.admind reachable on internal or external networks. Modern environments are effectively unaffected. No vendor, product, or version list is enumerated in the source bundle, so scope must be confirmed against local Solaris inventory.

Exploitation context

The CVE is not listed in CISA KEV, and the source bundle cites no active exploitation campaigns. Historically, insecure rpc.admind was a well-known misconfiguration abused during the late 1990s Solaris era, but no current exploitation evidence is provided in the referenced sources.

Researcher notes

Source bundle is sparse: no CVSS, no CWE, generic n/a vendor/product entries, and only an X-Force reference plus CVE Program records. Treat this as a configuration-class advisory tied to Solstice AdminSuite rpc.admind weak authentication mode. Validate against Sun/Oracle legacy documentation before assessing any live Solaris estate; do not extrapolate to non-Solaris RPC stacks.

Mitigation direction

  • Inventory any remaining Solaris hosts and identify systems running rpc.admind or Solstice AdminSuite.
  • Consult Sun/Oracle legacy Solaris hardening guidance for enabling secure mode on rpc.admind.
  • Disable rpc.admind entirely on systems that do not require remote Solstice administration.
  • Restrict RPC and portmapper access at the network layer to trusted management subnets only.
  • Plan migration off end-of-life Solaris platforms where feasible.

Validation and detection

  • Enumerate RPC services on Solaris hosts to confirm whether rpc.admind is registered and listening.
  • Verify the daemon's authentication mode against vendor documentation for secure versus insecure operation.
  • Review network ACLs and firewall rules to confirm RPC ports are not exposed beyond management enclaves.
  • Cross-check host inventory against configuration management to identify unmanaged legacy Solaris systems.
Prepared
Confidence
low
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-1999-0568 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.