Stripe credential exposure via hard-coded configuration key
Published Jul 3, 2023 · Updated Nov 6, 2024
Hard-coded credentials in The King's Temple Church Website 0.1.0 allow attackers to obtain a Stripe API key from public source code. The next.config.js file embeds the key in the versioned repository instead of loading it from protected secret storage. Access to the public repository is sufficient to recover the credential, enabling unauthorized Stripe transactions and access to customer information.
Summary
What happened
Hard-coded credentials in The King's Temple Church Website 0.1.0 allow attackers to obtain a Stripe API key from public source code. The next.config.js file embeds the key in the versioned repository instead of loading it from protected secret storage. Access to the public repository is sufficient to recover the credential, enabling unauthorized Stripe transactions and access to customer information.
The record
- CVE
- CVE-2023-36817
- Published
- Jul 3, 2023
- Updated
- Nov 6, 2024
- Vendor
- The King's Temple Church
- Product
- The King's Temple Church Website
- Classifications
- CWE-798, CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 2024Record 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== 0.1.0
- Affected versionversion=0.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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