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

> Physically proximate attackers can bypass the screen lock to execute arbitrary commands via the command dialog on unattended GNOME Shell workstations.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7221, GHSA-2fwf-gr55-x95r

## What is CVE-2013-7221?

CVE-2013-7221 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The automatic screen lock functionality in GNOME Shell (aka gnome-shell) before 3.10 does not prevent access to the "Enter a Command" dialog, which allows physically proximate attackers to execute arbitrary commands by leveraging an unattended workstation.

Weakness: CWE-264

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

It affects 1 product.


Products: Gnome Gnome-Shell.

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

Upgrade to a fixed version.

## Is CVE-2013-7221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8288](https://insights.sbomify.com/CVE-2017-8288/): Security feature bypass in n/a (high 8.1)
- [CVE-2014-7300](https://insights.sbomify.com/CVE-2014-7300/): Denial of service in n/a (high 7.2)
- [CVE-2010-4000](https://insights.sbomify.com/CVE-2010-4000/): Privilege escalation in n/a (medium 6.9)
- [CVE-2012-4427](https://insights.sbomify.com/CVE-2012-4427/): Code injection in n/a (medium 6.8)
- [CVE-2021-3982](https://insights.sbomify.com/CVE-2021-3982/): Privilege escalation in gnome-shell (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7221 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-7221 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-7221/ (Markdown: https://insights.sbomify.com/CVE-2013-7221/index.md)
```

## Sources

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

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