crawlseo before 0.2.5 Cleartext Storage of Google OAuth Tokens
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| crawlseo | crawlseo | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Crawlseo | Crawlseo |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.104% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | crawlseo before 0.2.5 Cleartext Storage of Google OAuth Tokens | |
| First Time appeared |
Crawlseo
Crawlseo crawlseo |
|
| Weaknesses | CWE-312 | |
| CPEs | cpe:2.3:a:crawlseo:crawlseo:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Crawlseo
Crawlseo crawlseo |
|
| References |
|
|
| Metrics |
cvssV3_1
|