# CVE-2021-29642: Information disclosure in n/a

> A crafted workspace folder in GistPad can redirect API calls, leaking GitHub access tokens to an attacker.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 30 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vxx6-78xm-pw3x

## What is CVE-2021-29642?

CVE-2021-29642 is a medium-severity vulnerability in n/a, published on 30 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GistPad before 0.2.7 allows a crafted workspace folder to change the URL for the Gist API, which leads to leakage of GitHub access tokens.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-29642?

It affects 1 product.


Products: Gistpad Project Gistpad.

## How do I fix CVE-2021-29642?

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

## Is CVE-2021-29642 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29642 and fix it if it is affected.

What it is: CVE-2021-29642 is a medium-severity vulnerability in n/a, published on 30 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-29642 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-2021-29642/ (Markdown: https://insights.sbomify.com/CVE-2021-29642/index.md)
```

## Sources

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

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