LiveActive security incident?Get immediate response
CVE Record

CVE-2009-4997: gnome-power-manager 2.27.92 does not properly implement the lock_on_suspend and lock_on_hibernate settings...

gnome-power-manager 2.27.92 does not properly implement the lock_on_suspend and lock_on_hibernate settings for locking 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, a related issue to CVE-2010-2532. NOTE: this issue exists because of a regression that followed a gnome-power-manager fix a few years earlier.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE describes a laptop screen-lock failure in gnome-power-manager 2.27.92. If a user expected the screen to lock when pressing suspend or hibernate, the setting may not work, leaving access possible after resume. The risk depends on physical access to an unattended affected laptop.

Executive priority

Treat as low urgency unless the organization still operates affected legacy GNOME laptops in shared or travel-heavy environments. The business risk is local device exposure, not remote compromise.

Technical view

The issue is an implementation regression affecting lock_on_suspend and lock_on_hibernate handling in gnome-power-manager 2.27.92. The CVE links it to CVE-2010-2532. The provided sources do not include CVSS, CWE, confirmed exploitation, or a specific vendor-fixed version.

Likely exposure

Likely limited to legacy Linux desktop environments using gnome-power-manager 2.27.92 or downstream builds carrying the regression. The source bundle does not identify broader affected CPEs or supported product versions.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not in KEV. Abuse requires physical proximity to an unattended affected laptop and a resume path where the expected lock is absent.

Researcher notes

Evidence is sparse. The CVE record names the faulty settings and regression context, while Launchpad bugs are the primary confirmations. Do not infer exploitability beyond physical resume access without additional vendor detail.

Mitigation direction

  • Check Ubuntu/GNOME guidance for corrected gnome-power-manager packages before making changes.
  • Update affected desktop packages through supported vendor channels when a corrected build is available.
  • Enforce lock-on-resume policy and verify it on managed laptops.
  • Limit unattended device risk with physical controls and full-disk encryption.

Validation and detection

  • Inventory Linux laptops for GNOME power management and gnome-power-manager version 2.27.92.
  • Confirm suspend and hibernate button actions trigger a locked screen on resume.
  • Review package changelogs or vendor advisories linked to the Launchpad bugs.
  • Document exceptions for unsupported or legacy desktop images.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2009-4997 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
3Source 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.