CVE-2023-36474
Summary
| CVE | CVE-2023-36474 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2023-06-28 22:15:00 UTC |
| Updated | 2023-07-07 14:54:00 UTC |
| Description | Interactsh is an open-source tool for detecting out-of-band interactions. Domains configured with interactsh server prior to version 1.0.0 were vulnerable to subdomain takeover for a specific subdomain, i.e `app.` Interactsh server used to create cname entries for `app` pointing to `projectdiscovery.github.io` as default, which intended to used for hosting interactsh web client using GitHub pages. This is a security issue with a self-hosted interactsh server in which the user may not have configured a web client but still have a CNAME entry pointing to GitHub pages, making them vulnerable to subdomain takeover. This allows a threat actor to host / run arbitrary client side code (cross-site scripting) in a user's browser when browsing the vulnerable subdomain. Version 1.0.0 fixes this issue by making CNAME optional, rather than default. |
Risk And Classification
Problem Types: CWE-79
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Projectdiscovery | Interactsh | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| deprecate default cname entry · Issue #136 · projectdiscovery/interactsh · GitHub | MISC | github.com | |
| Hostile Subdomain Takeover using Heroku/Github/Desk + more - Detectify Labs | MISC | labs.detectify.com | |
| Interactsh server < 1.0.0 Subdomain Takeover · Advisory · projectdiscovery/interactsh · GitHub | MISC | github.com | |
| Making app CNAME optional by Mzack9999 · Pull Request #155 · projectdiscovery/interactsh · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.