# CVE-2013-1050: Security feature bypass in n/a

> Physically proximate attackers can bypass screen locking and access unattended workstations due to a default configuration flaw in gnome-screensaver.

- **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:** 8 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wxh9-j377-5h7q

## What is CVE-2013-1050?

CVE-2013-1050 is a high-severity vulnerability in n/a, published on 8 Mar 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The default configuration in gnome-screensaver 3.5.4 through 3.6.0 sets the AutostartCondition line to fallback mode in the .desktop file, which prevents the program from starting automatically after login and allows physically proximate attackers to bypass screen locking and access an unattended workstation.

Weakness: CWE-264

## Which versions are affected by CVE-2013-1050?

It affects 1 product.


Products: Gnome Gnome Screensaver.

## How do I fix CVE-2013-1050?

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

## Is CVE-2013-1050 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1050 and fix it if it is affected.

What it is: CVE-2013-1050 is a high-severity vulnerability in n/a, published on 8 Mar 2013. 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-2013-1050 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-2013-1050/ (Markdown: https://insights.sbomify.com/CVE-2013-1050/index.md)
```

## Sources

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

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