Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a taint as prefix to payload URL does not work with DNS interactions #898

Closed
blackthorne opened this issue Jun 14, 2024 · 6 comments · Fixed by #918
Closed

Adding a taint as prefix to payload URL does not work with DNS interactions #898

blackthorne opened this issue Jun 14, 2024 · 6 comments · Fixed by #918
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@blackthorne
Copy link

Interactsh version:

v1.2.0

Current Behavior:

when I add an arbitrary taint as prefix to an interactsh payload it will only work for http but not dns.
So if my payload is cpjdvj4bajfald2br18gurjuymnd6gtyg.oast.site and I run dig TAINT_PREFFIX_cpjdvj4bajfald2br18gurjuymnd6gtyg.oast.site I get no hits on interactsh.

Expected Behavior:

Just like for http I expect to see a DNS interaction when using a prefix just like I would if I was browsing to http://TAINT_PREFFIX_cpjdvj4bajfald2br18gurjuymnd6gtyg.oast.site .

Steps To Reproduce:

  1. run interactsh and generate a <payload>
  2. run dig TAINT_PREFFIX_<payload> (or trigger a DNS request against it in your preferred way)
  3. verify that no hits are recorded in interactsh

Anything else:

The same behaviour is seen on the web app ( https://app.interactsh.com ).

@blackthorne blackthorne added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jun 14, 2024
@blackthorne
Copy link
Author

Any updates on this one? Thank you

@ehsandeep ehsandeep linked a pull request Jul 10, 2024 that will close this issue
@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Jul 15, 2024
@blackthorne
Copy link
Author

blackthorne commented Aug 2, 2024

Just as a FYI - I'm not sure if this is meant to be applied in app.interactsh.com but in my tests it still did not work.

@blackthorne
Copy link
Author

app.interactsh.com still not supporting dns correlation ids - any updates?

1 similar comment
@blackthorne
Copy link
Author

app.interactsh.com still not supporting dns correlation ids - any updates?

@dogancanbakir
Copy link
Member

dogancanbakir commented Sep 26, 2024

@blackthorne I've just deployed the new version with recent changes. Could you retry it?

@blackthorne
Copy link
Author

@dogancanbakir it works. thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants