├── Firebase-exploit.py ├── LICENSE ├── README.md ├── Sample-Report └── requirements.txt /Firebase-exploit.py: -------------------------------------------------------------------------------- 1 | #!/usr/bin/python3 2 | import subprocess 3 | import requests 4 | import json 5 | import os 6 | import sys 7 | import traceback 8 | from shutil import which 9 | from colorama import Fore 10 | 11 | url = 'https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=' 12 | headers = {"content-type": 'application/json'} 13 | 14 | 15 | def check_apktool(): 16 | try: 17 | if which("apktool"): 18 | return True 19 | else: 20 | return False 21 | except Exception as e: 22 | print(Fore.RED + f"[!] Error in checking apktool: {e}") 23 | 24 | 25 | # Decompiling the apk 26 | def decompile_apk(apk_file): 27 | try: 28 | print(Fore.BLUE + f"[+] Decompiling {os.path.basename(apk_file)}!") 29 | os.popen(f"apktool d {apk_file}").read() 30 | print(Fore.BLUE + "[+] Apk decompiled!") 31 | return apk.split(".")[0] 32 | except Exception as e: 33 | print(Fore.RED + f"[!] Error in decompiling apk: {e}") 34 | 35 | 36 | # Extracting the keys using both regex 37 | def extract_keys(_out_dir): 38 | try: 39 | output1 = subprocess.getoutput(f'grep -ProIR "AIzaSy[0-9A-Za-z_-]{{33}}" {_out_dir}') 40 | output2 = subprocess.getoutput(f'grep -ProIR "AAAA[A-Za-z0-9_-]{{7}}:[A-Za-z0-9_-]{{140}}" {_out_dir}') 41 | 42 | res = [] 43 | if output1: 44 | res1 = output1.splitlines() 45 | res.extend(res1) 46 | if output2: 47 | res2 = output2.splitlines() 48 | res.extend(res2) 49 | 50 | if not res: 51 | print(Fore.RED + "[-] No tokens found") 52 | exit() 53 | 54 | keys = [i.split(":")[1] for i in res] 55 | print(Fore.BLUE + f"[+] Found some tokens: {', '.join(list(set(keys)))}") 56 | return list(set(keys)) 57 | except Exception as e: 58 | print(Fore.RED + f"[!] Error in extracting keys: {e}") 59 | 60 | 61 | def validate_keys(key): 62 | try: 63 | r = requests.get(url + key) 64 | if r.status_code == 200: 65 | response_data = r.json() 66 | authorized_domains = response_data.get("authorizedDomains") 67 | if authorized_domains: 68 | 69 | filtered_domains = [domain for domain in authorized_domains if '.firebaseapp.com' in domain] 70 | return filtered_domains 71 | else: 72 | print(Fore.RED + f"[+] {key} is a valid server key, but authorizedDomains not found in the response") 73 | else: 74 | print(Fore.RED + f"[-] {key} is not a valid server key") 75 | except Exception as e: 76 | print(Fore.RED + f"[!] Error in validating keys: {e}") 77 | 78 | return None 79 | 80 | 81 | 82 | if __name__ == "__main__": 83 | try: 84 | if not check_apktool(): 85 | print(Fore.RED + "[!] Install apktool for decompiling the apk!") 86 | exit() 87 | apk = sys.argv[1] 88 | out_dir = decompile_apk(apk) 89 | server_keys = extract_keys(out_dir) 90 | if not server_keys: 91 | print(Fore.RED + "[-] FCM keys not found in extracted apk!") 92 | exit() 93 | 94 | valid_domains = set() 95 | for server_key in server_keys: 96 | domains = validate_keys(server_key) 97 | if domains: 98 | for domain in domains: 99 | domain_parts = domain.split(".firebaseapp.com") 100 | if len(domain_parts) > 0: 101 | authorized_domain = domain_parts[0] 102 | valid_domains.add(authorized_domain) 103 | print(Fore.GREEN + f"[+] Server Key = {server_key} | projectId = {authorized_domain}") 104 | else: 105 | pass 106 | print(Fore.BLUE + f"[+] Finished!") 107 | except: 108 | print(traceback.format_exc()) 109 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Mozilla Public License Version 2.0 2 | ================================== 3 | 4 | 1. Definitions 5 | -------------- 6 | 7 | 1.1. "Contributor" 8 | means each individual or legal entity that creates, contributes to 9 | the creation of, or owns Covered Software. 10 | 11 | 1.2. "Contributor Version" 12 | means the combination of the Contributions of others (if any) used 13 | by a Contributor and that particular Contributor's Contribution. 14 | 15 | 1.3. "Contribution" 16 | means Covered Software of a particular Contributor. 17 | 18 | 1.4. "Covered Software" 19 | means Source Code Form to which the initial Contributor has attached 20 | the notice in Exhibit A, the Executable Form of such Source Code 21 | Form, and Modifications of such Source Code Form, in each case 22 | including portions thereof. 23 | 24 | 1.5. "Incompatible With Secondary Licenses" 25 | means 26 | 27 | (a) that the initial Contributor has attached the notice described 28 | in Exhibit B to the Covered Software; or 29 | 30 | (b) that the Covered Software was made available under the terms of 31 | version 1.1 or earlier of the License, but not also under the 32 | terms of a Secondary License. 33 | 34 | 1.6. "Executable Form" 35 | means any form of the work other than Source Code Form. 36 | 37 | 1.7. "Larger Work" 38 | means a work that combines Covered Software with other material, in 39 | a separate file or files, that is not Covered Software. 40 | 41 | 1.8. "License" 42 | means this document. 43 | 44 | 1.9. "Licensable" 45 | means having the right to grant, to the maximum extent possible, 46 | whether at the time of the initial grant or subsequently, any and 47 | all of the rights conveyed by this License. 48 | 49 | 1.10. "Modifications" 50 | means any of the following: 51 | 52 | (a) any file in Source Code Form that results from an addition to, 53 | deletion from, or modification of the contents of Covered 54 | Software; or 55 | 56 | (b) any new file in Source Code Form that contains any Covered 57 | Software. 58 | 59 | 1.11. "Patent Claims" of a Contributor 60 | means any patent claim(s), including without limitation, method, 61 | process, and apparatus claims, in any patent Licensable by such 62 | Contributor that would be infringed, but for the grant of the 63 | License, by the making, using, selling, offering for sale, having 64 | made, import, or transfer of either its Contributions or its 65 | Contributor Version. 66 | 67 | 1.12. "Secondary License" 68 | means either the GNU General Public License, Version 2.0, the GNU 69 | Lesser General Public License, Version 2.1, the GNU Affero General 70 | Public License, Version 3.0, or any later versions of those 71 | licenses. 72 | 73 | 1.13. "Source Code Form" 74 | means the form of the work preferred for making modifications. 75 | 76 | 1.14. "You" (or "Your") 77 | means an individual or a legal entity exercising rights under this 78 | License. For legal entities, "You" includes any entity that 79 | controls, is controlled by, or is under common control with You. For 80 | purposes of this definition, "control" means (a) the power, direct 81 | or indirect, to cause the direction or management of such entity, 82 | whether by contract or otherwise, or (b) ownership of more than 83 | fifty percent (50%) of the outstanding shares or beneficial 84 | ownership of such entity. 85 | 86 | 2. License Grants and Conditions 87 | -------------------------------- 88 | 89 | 2.1. Grants 90 | 91 | Each Contributor hereby grants You a world-wide, royalty-free, 92 | non-exclusive license: 93 | 94 | (a) under intellectual property rights (other than patent or trademark) 95 | Licensable by such Contributor to use, reproduce, make available, 96 | modify, display, perform, distribute, and otherwise exploit its 97 | Contributions, either on an unmodified basis, with Modifications, or 98 | as part of a Larger Work; and 99 | 100 | (b) under Patent Claims of such Contributor to make, use, sell, offer 101 | for sale, have made, import, and otherwise transfer either its 102 | Contributions or its Contributor Version. 103 | 104 | 2.2. Effective Date 105 | 106 | The licenses granted in Section 2.1 with respect to any Contribution 107 | become effective for each Contribution on the date the Contributor first 108 | distributes such Contribution. 109 | 110 | 2.3. Limitations on Grant Scope 111 | 112 | The licenses granted in this Section 2 are the only rights granted under 113 | this License. No additional rights or licenses will be implied from the 114 | distribution or licensing of Covered Software under this License. 115 | Notwithstanding Section 2.1(b) above, no patent license is granted by a 116 | Contributor: 117 | 118 | (a) for any code that a Contributor has removed from Covered Software; 119 | or 120 | 121 | (b) for infringements caused by: (i) Your and any other third party's 122 | modifications of Covered Software, or (ii) the combination of its 123 | Contributions with other software (except as part of its Contributor 124 | Version); or 125 | 126 | (c) under Patent Claims infringed by Covered Software in the absence of 127 | its Contributions. 128 | 129 | This License does not grant any rights in the trademarks, service marks, 130 | or logos of any Contributor (except as may be necessary to comply with 131 | the notice requirements in Section 3.4). 132 | 133 | 2.4. Subsequent Licenses 134 | 135 | No Contributor makes additional grants as a result of Your choice to 136 | distribute the Covered Software under a subsequent version of this 137 | License (see Section 10.2) or under the terms of a Secondary License (if 138 | permitted under the terms of Section 3.3). 139 | 140 | 2.5. Representation 141 | 142 | Each Contributor represents that the Contributor believes its 143 | Contributions are its original creation(s) or it has sufficient rights 144 | to grant the rights to its Contributions conveyed by this License. 145 | 146 | 2.6. Fair Use 147 | 148 | This License is not intended to limit any rights You have under 149 | applicable copyright doctrines of fair use, fair dealing, or other 150 | equivalents. 151 | 152 | 2.7. Conditions 153 | 154 | Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted 155 | in Section 2.1. 156 | 157 | 3. Responsibilities 158 | ------------------- 159 | 160 | 3.1. Distribution of Source Form 161 | 162 | All distribution of Covered Software in Source Code Form, including any 163 | Modifications that You create or to which You contribute, must be under 164 | the terms of this License. You must inform recipients that the Source 165 | Code Form of the Covered Software is governed by the terms of this 166 | License, and how they can obtain a copy of this License. You may not 167 | attempt to alter or restrict the recipients' rights in the Source Code 168 | Form. 169 | 170 | 3.2. Distribution of Executable Form 171 | 172 | If You distribute Covered Software in Executable Form then: 173 | 174 | (a) such Covered Software must also be made available in Source Code 175 | Form, as described in Section 3.1, and You must inform recipients of 176 | the Executable Form how they can obtain a copy of such Source Code 177 | Form by reasonable means in a timely manner, at a charge no more 178 | than the cost of distribution to the recipient; and 179 | 180 | (b) You may distribute such Executable Form under the terms of this 181 | License, or sublicense it under different terms, provided that the 182 | license for the Executable Form does not attempt to limit or alter 183 | the recipients' rights in the Source Code Form under this License. 184 | 185 | 3.3. Distribution of a Larger Work 186 | 187 | You may create and distribute a Larger Work under terms of Your choice, 188 | provided that You also comply with the requirements of this License for 189 | the Covered Software. If the Larger Work is a combination of Covered 190 | Software with a work governed by one or more Secondary Licenses, and the 191 | Covered Software is not Incompatible With Secondary Licenses, this 192 | License permits You to additionally distribute such Covered Software 193 | under the terms of such Secondary License(s), so that the recipient of 194 | the Larger Work may, at their option, further distribute the Covered 195 | Software under the terms of either this License or such Secondary 196 | License(s). 197 | 198 | 3.4. Notices 199 | 200 | You may not remove or alter the substance of any license notices 201 | (including copyright notices, patent notices, disclaimers of warranty, 202 | or limitations of liability) contained within the Source Code Form of 203 | the Covered Software, except that You may alter any license notices to 204 | the extent required to remedy known factual inaccuracies. 205 | 206 | 3.5. Application of Additional Terms 207 | 208 | You may choose to offer, and to charge a fee for, warranty, support, 209 | indemnity or liability obligations to one or more recipients of Covered 210 | Software. However, You may do so only on Your own behalf, and not on 211 | behalf of any Contributor. You must make it absolutely clear that any 212 | such warranty, support, indemnity, or liability obligation is offered by 213 | You alone, and You hereby agree to indemnify every Contributor for any 214 | liability incurred by such Contributor as a result of warranty, support, 215 | indemnity or liability terms You offer. You may include additional 216 | disclaimers of warranty and limitations of liability specific to any 217 | jurisdiction. 218 | 219 | 4. Inability to Comply Due to Statute or Regulation 220 | --------------------------------------------------- 221 | 222 | If it is impossible for You to comply with any of the terms of this 223 | License with respect to some or all of the Covered Software due to 224 | statute, judicial order, or regulation then You must: (a) comply with 225 | the terms of this License to the maximum extent possible; and (b) 226 | describe the limitations and the code they affect. Such description must 227 | be placed in a text file included with all distributions of the Covered 228 | Software under this License. Except to the extent prohibited by statute 229 | or regulation, such description must be sufficiently detailed for a 230 | recipient of ordinary skill to be able to understand it. 231 | 232 | 5. Termination 233 | -------------- 234 | 235 | 5.1. The rights granted under this License will terminate automatically 236 | if You fail to comply with any of its terms. However, if You become 237 | compliant, then the rights granted under this License from a particular 238 | Contributor are reinstated (a) provisionally, unless and until such 239 | Contributor explicitly and finally terminates Your grants, and (b) on an 240 | ongoing basis, if such Contributor fails to notify You of the 241 | non-compliance by some reasonable means prior to 60 days after You have 242 | come back into compliance. Moreover, Your grants from a particular 243 | Contributor are reinstated on an ongoing basis if such Contributor 244 | notifies You of the non-compliance by some reasonable means, this is the 245 | first time You have received notice of non-compliance with this License 246 | from such Contributor, and You become compliant prior to 30 days after 247 | Your receipt of the notice. 248 | 249 | 5.2. If You initiate litigation against any entity by asserting a patent 250 | infringement claim (excluding declaratory judgment actions, 251 | counter-claims, and cross-claims) alleging that a Contributor Version 252 | directly or indirectly infringes any patent, then the rights granted to 253 | You by any and all Contributors for the Covered Software under Section 254 | 2.1 of this License shall terminate. 255 | 256 | 5.3. In the event of termination under Sections 5.1 or 5.2 above, all 257 | end user license agreements (excluding distributors and resellers) which 258 | have been validly granted by You or Your distributors under this License 259 | prior to termination shall survive termination. 260 | 261 | ************************************************************************ 262 | * * 263 | * 6. Disclaimer of Warranty * 264 | * ------------------------- * 265 | * * 266 | * Covered Software is provided under this License on an "as is" * 267 | * basis, without warranty of any kind, either expressed, implied, or * 268 | * statutory, including, without limitation, warranties that the * 269 | * Covered Software is free of defects, merchantable, fit for a * 270 | * particular purpose or non-infringing. The entire risk as to the * 271 | * quality and performance of the Covered Software is with You. * 272 | * Should any Covered Software prove defective in any respect, You * 273 | * (not any Contributor) assume the cost of any necessary servicing, * 274 | * repair, or correction. This disclaimer of warranty constitutes an * 275 | * essential part of this License. No use of any Covered Software is * 276 | * authorized under this License except under this disclaimer. * 277 | * * 278 | ************************************************************************ 279 | 280 | ************************************************************************ 281 | * * 282 | * 7. Limitation of Liability * 283 | * -------------------------- * 284 | * * 285 | * Under no circumstances and under no legal theory, whether tort * 286 | * (including negligence), contract, or otherwise, shall any * 287 | * Contributor, or anyone who distributes Covered Software as * 288 | * permitted above, be liable to You for any direct, indirect, * 289 | * special, incidental, or consequential damages of any character * 290 | * including, without limitation, damages for lost profits, loss of * 291 | * goodwill, work stoppage, computer failure or malfunction, or any * 292 | * and all other commercial damages or losses, even if such party * 293 | * shall have been informed of the possibility of such damages. This * 294 | * limitation of liability shall not apply to liability for death or * 295 | * personal injury resulting from such party's negligence to the * 296 | * extent applicable law prohibits such limitation. Some * 297 | * jurisdictions do not allow the exclusion or limitation of * 298 | * incidental or consequential damages, so this exclusion and * 299 | * limitation may not apply to You. * 300 | * * 301 | ************************************************************************ 302 | 303 | 8. Litigation 304 | ------------- 305 | 306 | Any litigation relating to this License may be brought only in the 307 | courts of a jurisdiction where the defendant maintains its principal 308 | place of business and such litigation shall be governed by laws of that 309 | jurisdiction, without reference to its conflict-of-law provisions. 310 | Nothing in this Section shall prevent a party's ability to bring 311 | cross-claims or counter-claims. 312 | 313 | 9. Miscellaneous 314 | ---------------- 315 | 316 | This License represents the complete agreement concerning the subject 317 | matter hereof. If any provision of this License is held to be 318 | unenforceable, such provision shall be reformed only to the extent 319 | necessary to make it enforceable. Any law or regulation which provides 320 | that the language of a contract shall be construed against the drafter 321 | shall not be used to construe this License against a Contributor. 322 | 323 | 10. Versions of the License 324 | --------------------------- 325 | 326 | 10.1. New Versions 327 | 328 | Mozilla Foundation is the license steward. Except as provided in Section 329 | 10.3, no one other than the license steward has the right to modify or 330 | publish new versions of this License. Each version will be given a 331 | distinguishing version number. 332 | 333 | 10.2. Effect of New Versions 334 | 335 | You may distribute the Covered Software under the terms of the version 336 | of the License under which You originally received the Covered Software, 337 | or under the terms of any subsequent version published by the license 338 | steward. 339 | 340 | 10.3. Modified Versions 341 | 342 | If you create software not governed by this License, and you want to 343 | create a new license for such software, you may create and use a 344 | modified version of this License if you rename the license and remove 345 | any references to the name of the license steward (except to note that 346 | such modified license differs from this License). 347 | 348 | 10.4. Distributing Source Code Form that is Incompatible With Secondary 349 | Licenses 350 | 351 | If You choose to distribute Source Code Form that is Incompatible With 352 | Secondary Licenses under the terms of this version of the License, the 353 | notice described in Exhibit B of this License must be attached. 354 | 355 | Exhibit A - Source Code Form License Notice 356 | ------------------------------------------- 357 | 358 | This Source Code Form is subject to the terms of the Mozilla Public 359 | License, v. 2.0. If a copy of the MPL was not distributed with this 360 | file, You can obtain one at http://mozilla.org/MPL/2.0/. 361 | 362 | If it is not possible or desirable to put the notice in a particular 363 | file, then You may include the notice in a location (such as a LICENSE 364 | file in a relevant directory) where a recipient would be likely to look 365 | for such a notice. 366 | 367 | You may add additional accurate notices of copyright ownership. 368 | 369 | Exhibit B - "Incompatible With Secondary Licenses" Notice 370 | --------------------------------------------------------- 371 | 372 | This Source Code Form is "Incompatible With Secondary Licenses", as 373 | defined by the Mozilla Public License, v. 2.0. 374 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Firebase-exploit 2 | Fast and customizable Firebase API and Project ID extractor. 3 | 4 | # Install Firebase-exploit 5 | 6 | ```sh 7 | git clone https://github.com/ProjectNull0/Firebase-exploit.git 8 | ``` 9 | 10 | ### Usage 11 | 12 | ```sh 13 | python3 Firebase-exploit.py app.apk 14 | ``` 15 | # How it works 16 | 17 | 1) Extract the Project ID and API key from the Python app 18 | 2) Use it on https://firebase.projectnull.tech/ 19 | 3) Check for the exploit ( If you have got a bug then RED alert will show ) 20 | 4) A sample report has been uploaded to the directory please check and can make a similar report 21 | 22 | Reach out to me on [Twitter](https://twitter.com/0day_exploit_) for Any support. 23 | 24 | 25 | ## Support 26 | If you like `Firebase-exploit` and it help you in work, money/bounty, pentesting, recon or just brings you happy feelings, please show your support! 27 | :stop_sign: **Please avoid opening GitHub issues for support requests or questions!** 28 | buy me a beer to keep me powered :) 29 | 30 | Buy Me A Beer 31 | -------------------------------------------------------------------------------- /Sample-Report: -------------------------------------------------------------------------------- 1 | # Titile :- 2 | Firebase takeover leads to tamper with website's static files 3 | 4 | # Discription ;- 5 | I found your Firebase configuration on a app res/values/strings.xml endpoint, the firebase is misconfigured, and an attacker can take over the firebase and tamper with the websites' static files.A "Firebase takeover" typically refers to a situation where someone gains unauthorized access to a Firebase project or account. Firebase is a platform by Google that provides various services for building and managing web and mobile applications. When a takeover occurs, it can have significant negative 6 | 7 | # Configuration:- 8 | 9 | { 10 | "apiKey": null, 11 | "authDomain": "null.firebaseapp.com", 12 | "databaseURL": "https://null.firebaseio.com", 13 | "projectId": null, 14 | "storageBucket": "null.appspot.com", 15 | "appId": "111", 16 | "measurementId": "111222" 17 | } 18 | 19 | please go to https://firebase.projectnull.tech/ , which is a PoC tool to demonstrate the bug. And use a browser open that html file, then input the ProjectID with , and the ApiKey with , and finally click the submit button twice, you will observe all websites' static files that were stored in the firebase storage, and a file named apoc.txt was uploaded to the firebase storage. It proved all static files in the firebase storage are vulnerable to tampering. 20 | 21 | # Step to reproduce 22 | 23 | In the site circle option 24 | 25 | Please see my screenshot in the attachment 26 | https://ibb.co/0nFnBW4 27 | 28 | # Impact 29 | 30 | Data Breach: Unauthorized access to a Firebase project can lead to the exposure of sensitive user data, including personal information, login credentials, and more. This can result in a data breach, which may have legal and financial consequences for the owner of the Firebase project. 31 | 32 | Data Manipulation: Attackers who gain control of a Firebase project can manipulate or delete data stored in the Firebase Realtime Database, Firestore, or Cloud Storage. This can disrupt the functionality of the associated application and harm its users. 33 | 34 | Unauthorized Access: A takeover can allow attackers to gain control over the Firebase project's resources and configurations. They may impersonate the legitimate owner and make unauthorized changes to the project, such as modifying authentication settings, cloud functions, or hosting configurations. 35 | 36 | Service Disruption: Attackers may intentionally disrupt the services hosted on Firebase, causing downtime for the application. This can result in a loss of revenue for businesses that rely on Firebase for their applications. 37 | 38 | Reputation Damage: A security breach can damage the reputation of the affected organization or developer. Users may lose trust in the service, and it can be challenging to regain that trust once it's lost. 39 | 40 | Legal Consequences: Depending on the nature of the takeover and the data involved, there may be legal consequences for the attacker as well as the owner of the Firebase project. Data protection laws, such as GDPR in Europe, can lead to fines and legal actions if user data is mishandled. 41 | 42 | To mitigate the impact of a Firebase takeover, it's essential to follow best practices for securing Firebase projects: 43 | 44 | Implement strong authentication methods, such as Firebase Authentication, and regularly review access permissions. 45 | 46 | Monitor Firebase usage and set up alerting for suspicious activities. 47 | 48 | Enable security rules for Firebase services to restrict access to authorized users and limit potential damage. 49 | 50 | Use Firebase's built-in security features, like Firebase Security Rules, to control access to your data. 51 | 52 | Educate your development team about security best practices and conduct security audits regularly. 53 | 54 | Be prepared with an incident response plan to quickly address and recover from security incidents. 55 | 56 | In case of a Firebase takeover, it's crucial to act swiftly to regain control of your Firebase project, investigate the breach, and notify affected users as required by data protection regulations. Additionally, you should work with security experts and legal counsel to manage the situation effectively. 57 | -------------------------------------------------------------------------------- /requirements.txt: -------------------------------------------------------------------------------- 1 | subprocess.run 2 | requests 3 | jsonlib 4 | os_sys 5 | traceback2 6 | colorama 7 | --------------------------------------------------------------------------------