-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
[CWE-918] Blind SSRF in /api/v1/comment #1677
Comments
Thank you for the report!
Could you please clarify this point? Title |
@paskal Hi! In this case, a minimal payload that I was able to reproduce was: |
Also, in my example, I was using a Burp Suite Collaborator as a part of Burp Suite. For development purposes, you may try to use it too. Another pay-free variant is http://webhook.site/. I hope it'll be helpful for you. |
What's the problem with |
|
Thanks for fast resolve! You're the best:)) |
@jet-pentest thanks for the report again! Please let us know if you would be able to reproduce anything else on https://remark42.com/demo/, that's very important information for us. |
Hi! I found an issue in remark42 engine.
When field "title" is missing in comment request and attacker send a malicious URL which is a part of locator struct on POST request to
/api/v1/comment?site=<SITE_ID>
, it leads to Blind SSRF vulnerability.As example, malicious URL looks like this:
{"text":"qweqwe","locator":{"site":"remark","url":"https://j5pxshabxb5037lms6z182pkjbp4d01p.oastify.com"}}
This malicious JSON in request to
/api/v1/comment?site=<SITE_ID>
leads to Blind SSRFAs another way, malicious field "title", which should be fully cutted by sanitizer, also leads to blind SSRF.
The text was updated successfully, but these errors were encountered: