Closed omk4r72 closed 3 months ago
If this issue affects you, please react with a 👍 (thumbs up emoji) to the initial post.
Your feedback helps us prioritize which bugs to investigate and address first.
@omk4r72 Thanks for reporting this. Unfortunately, I wasn't able to fully understand the description and reproduce this case. Are you referring to an app deployed on Community Cloud or apps in general?
STEP -----------------------STEP 1) FIRST I WILL DORK THE SUBDOMAIN 2) GREP THE IP FROM THE SHODAN 3) CHECK THE PORT OF THE FILTERED IP 4) AND PERFORM THE DOS ATTACK & CHECK THE MAIN DOMAIN
the title is scary but I need a translator
If the problem is about some WebRTC-based image application, I'd say it's more or less expected. Connecting via "real" IP of peers is how WebRTC works.
We looked into this issue more closely but couldn't find any trace of core Streamlit or Community Cloud exposing an internal IP. It could be related to some external dependency (e.g., webrtc) or some misconfiguration of the instance on which the app is deployed, but that is outside of our control. If you have any other relevant information, please share it here.
Checklist
Summary
INTERNAL IP LEAKED :))))
Reproducible Code Example
Steps To Reproduce
FOR THE FINDING THE BUG I DORK THE SOME SUBDOMAIN BRUTEFORCE THE DOMAIN AND GET THE INTERNAL IP FORM THE SHODAN AND TRY TO DOS ATTACK ON THE IP SO SUCCESSFULLY DOS ATTACK ON THE INTERNAL IP OF THE DOMAIN
Expected Behavior
ATTACKER CAN DOS THIS INTERNAL IP AND DOWN THE SERVER OF THE DOMAIN
Current Behavior
CAN LEAKED THE IINTERNAL IP
Is this a regression?
Debug info
Additional Information
NO "))))