Potential security issue

[JamieSlome]

Hey there!

I belong to an open source security research community, and a member (@ranjit-git) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

[tomas]

Hi @JamieSlome, you can find my email address at the package.json file in this repository. Feel free to contact me, I'll be happy to discuss and fix any potential security issues.

[JamieSlome]

Hello @tomas, thanks for the response.

If it is easier for you, you can directly see the report here:

https://huntr.dev/bounties/03ac704d-6ccf-4d4b-bed3-f123f4e31dcd/

It is private and only accessible to yourself! ❤️

[tomas]

I'd prefer to discuss it via email. Otherwise feel free to submit a PR. :)

[JamieSlome]

@tomas - e-mail sent! 📧

[ranjit-git]

hi @tomas submitted the PR fix for this bug #386
You can also read full bug report here https://huntr.dev/bounties/03ac704d-6ccf-4d4b-bed3-f123f4e31dcd/
let me know here if you having issue to view the report .