LiveActive security incident?Get immediate response
CVE Record

CVE-2010-2532: lxsession-logout in lxsession in LXDE, as used on SUSE openSUSE 11.3 and other platforms, does not lock the...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue concerns LXDE’s logout dialog not locking the screen when Suspend or Hibernate is selected. The business risk is local, not remote: someone physically near an unattended laptop may access the resumed session. The CVE record also notes disagreement about whether this behavior is always a vulnerability. Exposure is most plausible on LXDE desktop laptops where users suspend or hibernate from lxsession-logout and no separate lock-on-suspend policy is enforced. The bundle does not identify a complete vendor, product, or version list beyond openSUSE 11.3 and other platforms. Treat as a low-priority physical-access hardening issue unless your environment has shared workspaces, travel-heavy laptop users, or sensitive unlocked sessions. Prioritize policy enforcement over emergency response. Mitigation focus: Check distribution or LXDE vendor guidance for package updates or configuration advice.; Require screen locking before suspend and hibernate on managed endpoints.; Set desktop power-management policy to authenticate on resume where supported..

Prepared

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-2010-2532 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
4Source links

CVSS and timeline data

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

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.