# CVE-2006-7240: Security feature bypass in n/a

> Attackers with physical access can bypass screen locking on suspend or hibernate, gaining unauthorized access to the system.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2010
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2006-7240, GHSA-fg74-hrjv-3hpw

## What is CVE-2006-7240?

CVE-2006-7240 is a high-severity vulnerability in n/a, published on 7 Sep 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

gnome-power-manager 2.14.0 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.

Weakness: CWE-264

## Which versions are affected by CVE-2006-7240?

It affects 1 product.


Products: Gnome Power Manager.

## How do I fix CVE-2006-7240?

Apply the vendor's patch.

## Is CVE-2006-7240 being exploited?

There is no known exploitation of CVE-2006-7240 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2009-4997](https://insights.sbomify.com/CVE-2009-4997/): Security feature bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7240 and fix it if it is affected.

What it is: CVE-2006-7240 is a high-severity vulnerability in n/a, published on 7 Sep 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7240 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-7240/ (Markdown: https://insights.sbomify.com/CVE-2006-7240/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7240
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7240
- OSV: https://osv.dev/vulnerability/CVE-2006-7240

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-7240/
Summaries are generated and may contain mistakes; the official description above is the record.