crawlseo before version 0.2.5 contains a cleartext storage vulnerability that allows attackers with database read access to obtain Google OAuth access and refresh tokens stored unencrypted in the User.googleTokens column. Attackers can read the plaintext long-lived refresh tokens from a compromised or exposed Postgres database to gain indefinite, unauthenticated access to all registered users' Google Search Console data.
Attack Parameters
Attack Vector
Local
Requires local access
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
High
Admin privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://gist.github.com/mansurmavlankulov/47cb8e183fec39a7afe599d1082a3399
disclosure@vulncheck.com
https://github.com/crawlseo/crawlseo/commit/2ce0b4b2bdd6047e0a9ede037fd35538196…
disclosure@vulncheck.com
https://github.com/crawlseo/crawlseo/releases/tag/v0.2.5
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/crawlseo-before-cleartext-storage-of-googl…
disclosure@vulncheck.com