# CVE-2023-36612: Path traversal in n/a

> Attackers can write arbitrary files and redirect sensitive server responses to third-party apps via malicious intents in the Basecamp Android application.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-97cm-f92p-p28q

## What is CVE-2023-36612?

CVE-2023-36612 is a high-severity path traversal vulnerability in n/a, published on 25 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal can occur in the Basecamp com.basecamp.bc3 application before 4.2.1 for Android, which may allow an attacker to write arbitrary files in the application's private directory. Additionally, by using a malicious intent, the attacker may redirect the server's responses (containing sensitive information) to third-party applications by using a custom-crafted deeplink scheme.

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

## Which versions are affected by CVE-2023-36612?

It affects 1 product.


Products: Basecamp Basecamp.

## How do I fix CVE-2023-36612?

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

## Is CVE-2023-36612 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36612 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36612 and fix it if it is affected.

What it is: CVE-2023-36612 is a high-severity path traversal vulnerability in n/a, published on 25 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36612 exists.

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

## Sources

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

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