# CVE-2016-6902: Security feature bypass in n/a

> Authenticated users can bypass lshell restrictions to execute arbitrary commands, leading to potential privilege escalation.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f3r7-j2g2-9mjw, PYSEC-2017-153, UBUNTU-CVE-2016-6902

## What is CVE-2016-6902?

CVE-2016-6902 is a critical vulnerability in n/a, published on 24 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

lshell 0.9.16 allows remote authenticated users to break out of a limited shell and execute arbitrary commands.

Weakness: CWE-264

## Which versions are affected by CVE-2016-6902?

1 open source package ship an affected version, including limited-shell. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `limited-shell` | PyPI | All versions to 0.9.16 | None |

Products: Lshell Project Lshell.

## How do I fix CVE-2016-6902?

Upgrade to a fixed version.

## Is CVE-2016-6902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6903](https://insights.sbomify.com/CVE-2016-6903/): Security feature bypass in n/a (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6902 and fix it if it is affected.

What it is: CVE-2016-6902 is a critical vulnerability in n/a, published on 24 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6902 in the wild and no public exploit code.

Affected packages and fixed versions:
- limited-shell (PyPI): affected all versions up to 0.9.16; no fix listed

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-2016-6902/ (Markdown: https://insights.sbomify.com/CVE-2016-6902/index.md)
```

## Sources

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

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