OAST: Interactsh: correlationId with prefix characters needs a dot as separator

Is your feature request related to a problem? Please describe. Interactsh parses the incoming DNS Name, URL etc. and tries to extract a correlationId. But a dot between arbitrary prefixing characters and the correlationId is required.

• Does not work: abc<correlationId>.interact.sh -> abc123456789.interact.sh
• Does work: abc.<correlationId>.interact.sh -> abc.123456789.interact.sh

getNewPayload() does not consider this currently.

Describe the solution you’d like We should implement that in a general way and append a single character with a dot in front of the correlationId

Additional context Add any other context or screenshots about the feature request here. https://github.com/zaproxy/zap-extensions/pull/3427

Would you like to help implementing this feature? yes

[thc202]

The problem is that it’s splitting on dots and checking the length is 33 (the 20 + 13) https://github.com/projectdiscovery/interactsh/blob/c7a1b32a1a3b11aa131dd3438d85c4f4c3386cee/pkg/server/dns_server.go#L152 before that, so if more data is there it will not match, changing Interactsh to cope with that case might be better in the long term.

[ehsandeep]

The problem is that it’s splitting on dots and checking the length is 33 (the 20 + 13) https://github.com/projectdiscovery/interactsh/blob/c7a1b32a1a3b11aa131dd3438d85c4f4c3386cee/pkg/server/dns_server.go#L152 before that, so if more data is there it will not match, changing Interactsh to cope with that case might be better in the long term.

This is now resolved with the latest release of interactsh server, i.e v1.0.2