# CVE-2022-39304: ghinstallation returns app JWT in error responses

> An attacker can obtain short-lived GitHub App JWTs from error responses in the ghinstallation Go library, potentially allowing unauthorized API access.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Dec 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-h4q8-96p6-jcgr, GO-2022-1178

## What is CVE-2022-39304?

CVE-2022-39304 is a medium-severity vulnerability in bradleyfalzon ghinstallation, published on 20 Dec 2022. 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

ghinstallation provides transport, which implements http.RoundTripper to provide authentication as an installation for GitHub Apps. In ghinstallation version 1, when the request to refresh an installation token failed, the HTTP request and response would be returned for debugging. The request contained the bearer JWT for the App, and was returned back to clients. This token is short lived (10 minute maximum). This issue has been patched and is available in version 2.0.0.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

3 open source packages ship an affected version, including github.com/bradleyfalzon/ghinstallation. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bradleyfalzon/ghinstallation` | Go | All versions | 1.1.2-0.20210308182858-d24f14f8be70 |
| `github.com/bradleyfalzon/ghinstallation` | Go | All versions | 2.0.0 |
| `github.com/bradleyfalzon/ghinstallation` | Go | All versions | 2.0.0 |

Products: Ghinstallation Project Ghinstallation.

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

Upgrade github.com/bradleyfalzon/ghinstallation to a fixed version for your release line: 1.1.2-0.20210308182858-d24f14f8be70 or 2.0.0.

## Is CVE-2022-39304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39304 is a medium-severity vulnerability in bradleyfalzon ghinstallation, published on 20 Dec 2022. 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-2022-39304 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/bradleyfalzon/ghinstallation (Go): affected all versions; fixed in 1.1.2-0.20210308182858-d24f14f8be70
- github.com/bradleyfalzon/ghinstallation (Go): affected all versions; fixed in 2.0.0
- github.com/bradleyfalzon/ghinstallation (Go): affected all versions; fixed in 2.0.0

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

## Sources

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

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