# CVE-2009-4996: Security feature bypass in n/a

> Xfce4-session fails to lock the screen during suspend or hibernate, allowing physically proximate attackers to access an unattended laptop.

- **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:** No
- **Published:** 7 Sep 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9282-mfvf-vv5h

## What is CVE-2009-4996?

CVE-2009-4996 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

Xfce4-session 4.5.91 in Xfce 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, a related issue to CVE-2010-2532.  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

Weakness: CWE-264

## Which versions are affected by CVE-2009-4996?

It affects 1 product.


Products: Xfce Xfce.

## How do I fix CVE-2009-4996?

No fix has been published for CVE-2009-4996 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-4996 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6532](https://insights.sbomify.com/CVE-2007-6532/): Use after free in n/a (critical 10.0)
- [CVE-2007-6531](https://insights.sbomify.com/CVE-2007-6531/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4996 and fix it if it is affected.

What it is: CVE-2009-4996 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-2009-4996 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-2009-4996/ (Markdown: https://insights.sbomify.com/CVE-2009-4996/index.md)
```

## Sources

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

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