File write failure on scan (Burp on Windows 10) about burp-js-miner HOT 3 CLOSED

Hello,

This behavior is intended. Just to clarify, these errors can occur during the JS Source Mapper scans (active or passive).

It seems the target website you were scanning had path traversal characters in the sources field(s) of the JS map files or base64 inline ones, which could lead to writing data outside of the intended directory.

Since this is extremely undesirable due to obvious security concerns, the scanner stops and throw these errors.

A better failover mechanism would be to store the files in the "tmp" directory for example. I can improve that in a future release.

from burp-js-miner.

sanitize to remove ../ and save to root ?

from burp-js-miner.

In general, block-listing is not a good approach from a security point of view.

Nevertheless, I double checked the code and did some testing, it seems that my earlier suggestion was already implemented - bad memory here sorry.

So even though these errors were triggered, the files should still be stored on your system in the "tmp" folder, can you please double check and confirm that?
Folder location should be in Burp's JS source mapper issue, which follows the following pattern:

<your-home-directory>/.BurpSuite/JS-Miner/<your-target-website.com>-<timeStamp>/tmp

from burp-js-miner.