GitHub token exposure via public runtime configuration
Published Apr 18, 2023 · Updated Feb 5, 2025
Credential exposure in NuxtLabs @nuxtlabs/github-module before 1.6.2 allows remote attackers to obtain a configured GitHub token. The module copies options.token or GITHUB_TOKEN into nuxt.options.runtimeConfig.public.github, making the credential available to client code. A Nuxt application must configure the module with a token; exposure grants the token's assigned GitHub repository permissions.
Summary
What happened
Credential exposure in NuxtLabs @nuxtlabs/github-module before 1.6.2 allows remote attackers to obtain a configured GitHub token. The module copies options.token or GITHUB_TOKEN into nuxt.options.runtimeConfig.public.github, making the credential available to client code. A Nuxt application must configure the module with a token; exposure grants the token's assigned GitHub repository permissions.
The record
- CVE
- CVE-2023-2138
- Published
- Apr 18, 2023
- Updated
- Feb 5, 2025
- Vendor
- NuxtLabs
- Product
- @nuxtlabs/github-module
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2023CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.6.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo