CVE-1999-1432
Summary
| CVE | CVE-1999-1432 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 1998-07-16 04:00:00 UTC |
| Updated | 2025-04-03 01:03:51 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v2.0 7.5 from [email protected]
AV:N/AC:L/Au:N/C:P/I:P/A:P
Problem Types: NVD-CWE-Other | n/a
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
LowAuthentication
NoneConfidentiality
PartialIntegrity
PartialAvailability
PartialAV:N/AC:L/Au:N/C:P/I:P/A:P
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Sun | Solaris | 2.4 | All | x86 | All |
| Operating System | Sun | Solaris | 2.5 | All | x86 | All |
| Operating System | Sun | Solaris | 2.5.1 | All | ppc | All |
| Operating System | Sun | Solaris | 2.5.1 | All | x86 | All |
| Operating System | Sun | Solaris | 2.6 | All | All | All |
| Operating System | Sun | Sunos | - | All | All | All |
| Operating System | Sun | Sunos | 5.4 | All | All | All |
| Operating System | Sun | Sunos | 5.5 | All | All | All |
| Operating System | Sun | Sunos | 5.5.1 | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| 'Security risk with powermanagemnet on Solaris 2.6' - MARC | af854a3a-2127-422b-91ae-364da2661108 | marc.info | |
| Solaris power management Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.