Skip to content

Warn when interactsh server lacks IPv6 (AAAA) records#1396

Merged
Mzack9999 merged 2 commits into
devfrom
1391-ipv6-warning
Jul 2, 2026
Merged

Warn when interactsh server lacks IPv6 (AAAA) records#1396
Mzack9999 merged 2 commits into
devfrom
1391-ipv6-warning

Conversation

@dogancanbakir

Copy link
Copy Markdown
Member

Closes #1391

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 868069e4-6c59-4613-99e9-41fe7457e427

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 1391-ipv6-warning

Comment @coderabbitai help to get the list of available commands.

@dogancanbakir
dogancanbakir requested a review from Mzack9999 June 30, 2026 16:02
@dogancanbakir dogancanbakir linked an issue Jul 1, 2026 that may be closed by this pull request
@bert128

bert128 commented Jul 1, 2026

Copy link
Copy Markdown

When the selected server publishes no AAAA records, the client prints a warning so that interactions from IPv6-only sources are not silently missed and mistaken for the absence of a vulnerability.

There's more to it than that...

Dual stack sources will be downgraded to legacy IP, which means that:

  1. you may not be aware that they are dual stack at all
  2. you will not discover the v6 addresses, which are harder to discover eg through sequential scans, and more likely to be an individual host rather than a shared nat gateway.

Also separate issue is that the default public servers listed on the project page have no v6 support.

@Mzack9999

Copy link
Copy Markdown
Member

Thanks, you're right about the impact. Just to be clear on scope: this PR only adds a warning so people don't confuse "no interaction" with "not vulnerable" when the target is IPv6 only. It doesn't fix the deeper issues you mention.

The dual stack downgrade is a real problem. Collapsing a dual stack source to its IPv4 address hides the v6 address, which is harder to find by scanning and more likely to be a single host than a shared NAT gateway. Capturing and reporting the source IPv6 properly is a bigger change on the server side. Tracked in #1398.

The default public servers not having AAAA records is a separate infra fix, unrelated to the client code. Tracked in #1399.

@Mzack9999
Mzack9999 merged commit 4a362ec into dev Jul 2, 2026
9 checks passed
@Mzack9999
Mzack9999 deleted the 1391-ipv6-warning branch July 2, 2026 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Default servers do not support IPv6, no warning

3 participants