CVE-2010-2532
Summary
| CVE | CVE-2010-2532 |
|---|---|
| State | PUBLISHED |
| Assigner | redhat |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2010-09-03 20:00:03 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | lxsession-logout in lxsession in LXDE, as used on SUSE openSUSE 11.3 and other platforms, does not lock the screen when the Suspend or Hibernate button is pressed, which might make it easier for physically proximate attackers to access an unattended laptop via a resume action. NOTE: there is no general agreement that this is a vulnerability, because separate control over locking can be an equally secure, or more secure, behavior in some threat environments. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
LocalAccess Complexity
LowAuthentication
NoneConfidentiality
CompleteIntegrity
CompleteAvailability
CompleteAV:L/AC:L/Au:N/C:C/I:C/A:C
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Bug 622083 – VUL-0: lxsession-logout should lock the screen before suspending/hibernating/switching users | af854a3a-2127-422b-91ae-364da2661108 | bugzilla.novell.com | |
| [security-announce] SUSE Security Summary Report: SUSE-SR:2010:014 | af854a3a-2127-422b-91ae-364da2661108 | lists.opensuse.org | |
| oss-security - CVE request: lxsession-logout | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| oss-security - Re: CVE request: lxsession-logout | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| Access Denied | af854a3a-2127-422b-91ae-364da2661108 | bugzillafiles.novell.org | |
| 614608 – (CVE-2010-2532) CVE-2010-2532 lxsession: does not lock the screen before suspending/hibernating/switching users | af854a3a-2127-422b-91ae-364da2661108 | bugzilla.redhat.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.