# CVE-2022-2653: Path Traversal in plankanban/planka

> Attackers can exploit path traversal to read sensitive configuration files and environment variables containing database credentials.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5c4f-cr5c-fm9x

## What is CVE-2022-2653?

CVE-2022-2653 is a high-severity path traversal vulnerability in plankanban/planka, published on 4 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

With this vulnerability an attacker can read many sensitive files like configuration files, or the /proc/self/environ file, that contains the environment variable used by the web server that includes database credentials. If the web server user is root, an attacker will be able to read any file in the system.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-2653?

It affects 1 product.


Products: Planka Planka.

## How do I fix CVE-2022-2653?

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

## Is CVE-2022-2653 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2653 and fix it if it is affected.

What it is: CVE-2022-2653 is a high-severity path traversal vulnerability in plankanban/planka, published on 4 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2653 in the wild and no public exploit code.

Affected product: plankanban/planka. 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-2022-2653/ (Markdown: https://insights.sbomify.com/CVE-2022-2653/index.md)
```

## Sources

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

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