CVE-1999-1432: n/a vulnerability

CVE-1999-1432: Power management (Powermanagement) on Solaris 2.4 through 2.6 does not start the xlock process until after...

Power management (Powermanagement) on Solaris 2.4 through 2.6 does not start the xlock process until after the sys-suspend has completed, which allows an attacker with physical access to input characters to the last active application from the keyboard for a short period after the system is restoring, which could lead to increased privileges.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 1, 2024, 17:11 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-1999-1432 is a historical Solaris local-console issue. During resume from suspend, xlock starts only after sys-suspend completes, leaving a short period where someone at the keyboard may type into the previously active application. Business risk is mainly for legacy Solaris systems with physical access exposure. Likely exposure is limited to legacy Solaris 2.4 through 2.6 systems using power management suspend with local keyboard access. This is not described as remotely exploitable. Modern environments are exposed only if these legacy systems remain operational in labs, industrial settings, or older administrative workstations. Prioritize this for environments that still run legacy Solaris with shared or weakly controlled physical access. It is not an internet-scale emergency, but it matters where privileged sessions could remain open during suspend and resume. Mitigation focus: Inventory Solaris 2.4 through 2.6 systems with power management or sys-suspend enabled.; Check Sun/Oracle or platform guidance for any historical patch, configuration change, or compensating control.; Restrict console and keyboard access to affected systems..

Prepared: Jul 1, 2026, 08:03 UTC (UTC+00:00)

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-1432 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: Mar 9, 2002, 05:00 UTC (UTC+00:00)

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

1Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5

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.