Skip to content

ghinstallation returns app JWT in error responses

Moderate severity GitHub Reviewed Published Dec 19, 2022 in bradleyfalzon/ghinstallation • Updated Aug 28, 2023

Package

gomod github.com/bradleyfalzon/ghinstallation (Go)

Affected versions

< 2.0.0

Patched versions

2.0.0

Description

Impact

In ghinstallation v1, when the request to refresh an installation token failed, the HTTP request and response would be returned for debugging.

https://github.com/bradleyfalzon/ghinstallation/blob/24e56b3fb7669f209134a01eff731d7e2ef72a5c/transport.go#L172-L174

The request contained the bearer JWT for the App, and was returned back to clients. This token is short lived (10 minute maximum).

Patches

  • This has already been patched in d24f14f8be70d94129d76026e8b0f4f9170c8c3e, and is available in releases >= v2.0.0.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

References

@bradleyfalzon bradleyfalzon published to bradleyfalzon/ghinstallation Dec 19, 2022
Published to the GitHub Advisory Database Dec 19, 2022
Reviewed Dec 19, 2022
Published by the National Vulnerability Database Dec 20, 2022
Last updated Aug 28, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2022-39304

GHSA ID

GHSA-h4q8-96p6-jcgr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.