Skip to content
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.

Server-side request forgery vulnerability (SSRF) #60

Closed
kkin77 opened this issue Sep 14, 2021 · 2 comments
Closed

Server-side request forgery vulnerability (SSRF) #60

kkin77 opened this issue Sep 14, 2021 · 2 comments

Comments

@kkin77
Copy link

kkin77 commented Sep 14, 2021

Describe the bug
Server-side request forgery vulnerability (SSRF)

To Reproduce
Steps to reproduce the behavior:
1.go to 'acp/acp.php?tn=pages&sub=index'
2. Enter the intranet address in the box to request
3. Can make a request to the intranet

Screenshots
image

request packet

image

Locate the vulnerable code /acp/core/pages.index.php
The start_index parameter calls the function fc_crawler

image

Tracing the fc_crawler function
Locate the vulnerable code /acp/core/functions_index.php

image

Continue to track the fc_loadSourceCode function

image

image

dict protocol for request

dict://ip:port

image

Use gopher protocol for request
gopher://192.168.172.114:9333/aaaaa
image

Led to the SSRF vulnerability

Desktop (please complete the following information):

  • OS: MacOS
  • Browser all
  • Version last version
patkon added a commit that referenced this issue Sep 15, 2021
We check if the starting point for indexing pages is a permitted page. Issue #60
@patkon
Copy link
Member

patkon commented Sep 15, 2021

I'm a little at a loss about this problem. I hope checking the starting point fixes the problem?

@kkin77
Copy link
Author

kkin77 commented Sep 17, 2021

Sorry, I haven’t seen it these days, you can fix it like this
The port for restricting requests can only be port 80, and only HTTP and HTTPS requests are allowed.
Restrict the intellectual property that cannot access the intranet to prevent attacks on the intranet.
Prohibit 302, 301 jump

patkon added a commit that referenced this issue Sep 26, 2021
We only allow http and https for base url in settings.
See comments from issue #60
@patkon patkon closed this as completed Jan 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants