Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unexpected results when manually calling getInteractshService.deregister()

See original GitHub issue

Describe the bug

When manually calling the function Java.type("org.parosproxy.paros.control.Control").getSingleton().getExtensionLoader().getExtension("ExtensionOast").getInteractshService().deregister() I would expect the OAST canaries defined to be reset to allow for a new one to be used, it would appear the code ends early on InteractshService.java#278 if the code returned is not 200.

Steps to reproduce the behavior

Start a interactsh OOB server
Let the client sit for a few days until the interactsh server loses the correlation-id
Call Java.type(“org.parosproxy.paros.control.Control”).getSingleton().getExtensionLoader().getExtension(“ExtensionOast”).getInteractshService().deregister()

Expected behavior

I would expect the de register option to clear the current server payload listed regardless of the returned code from the OAST service.

Software versions

2.11.1

Screenshots

No response

Errors from the zap.log file

[ZAP-ScriptExecutor-Deregiser OAST.js] WARN InteractshService - Error during interactsh deregister, due to bad HTTP code 400. Content: {“error”:“could not remove id: could not get correlation-id from cache”}