Credential disclosure via unfiltered build-time authentication configuration
Published Jul 15, 2021 · Updated Aug 3, 2024
Credential exposure in Gatsby's gatsby-source-wordpress before 4.0.8 and 5.0.0 through 5.9.1 allows remote attackers to read HTTP Basic credentials. The plugin copies the htaccess username and password from the auth section of gatsby-config.js into the public app.js bundle instead of filtering those secrets during the build. Exposure requires initialized .htaccess authentication settings and access to the built bundle; the disclosed data is limited to those configured credentials.
Summary
What happened
Credential exposure in Gatsby's gatsby-source-wordpress before 4.0.8 and 5.0.0 through 5.9.1 allows remote attackers to read HTTP Basic credentials. The plugin copies the htaccess username and password from the auth section of gatsby-config.js into the public app.js bundle instead of filtering those secrets during the build. Exposure requires initialized .htaccess authentication settings and access to the built bundle; the disclosed data is limited to those configured credentials.
The record
- CVE
- CVE-2021-32770
- Published
- Jul 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Gatsby
- Product
- Gatsby
- Classifications
- CWE-522, CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=< 4.0.8
- Affected versionversion=>= 5.0.0, < 5.9.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