Skip to content

Subdomain Takeover in Interactsh server

Moderate severity GitHub Reviewed Published Jan 24, 2022 in projectdiscovery/interactsh • Updated Nov 10, 2023

Package

gomod github.com/projectdiscovery/interactsh (Go)

Affected versions

< 1.0.0

Patched versions

1.0.0

Description

A domain configured with interactsh server was vulnerable to subdomain takeover for specfic subdomain, i.e app, Interactsh server before < 1.0.0 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. It turns out to be 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 issue was initially reported to us as a subdomain takeover for one of our domains that runs interactsh server by Melih at [email protected], and after conducting an internal investigation, we determined that it was an issue with the default config of interactsh server affecting all the server running self-hosted instance of interactsh, as a result - cname entry has been removed in the latest release.

Impact

This allows one to host / run arbitrary client side code (XSS) in a user's browser when browsing the vulnerable subdomain, for more details on the impact, please read this detailed blogpost from Detectify.

Patches

Update to Interactsh server v1.0.0 with go install -v github.com/projectdiscovery/interactsh/cmd/interactsh-server@latest

References

projectdiscovery/interactsh#136

For more information

If you have any questions or comments about this advisory:

References

@ehsandeep ehsandeep published to projectdiscovery/interactsh Jan 24, 2022
Reviewed Jan 24, 2022
Published to the GitHub Advisory Database Jan 27, 2022
Published by the National Vulnerability Database Jun 28, 2023
Last updated Nov 10, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.089%
(39th percentile)

Weaknesses

CVE ID

CVE-2023-36474

GHSA ID

GHSA-m36x-mgfh-8g78
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.