{"uuid": "698e23c2-1897-49d9-ab56-62e4ac4df46d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-22205", "type": "seen", "source": "https://t.me/hacking_Attack/30017", "content": "Black Hat Ethical Hacking\nOver 30,000 GitLab servers still unpatched against critical bug\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Over 30,000 GitLab servers still unpatched against critical bugPost Views: 115 \nReading Time: 1 Minute\nA critical unauthenticated, remote code execution GitLab flaw fixed on April 14, 2021, remains exploitable, with over 50% of deployments remaining unpatched.\nThe vulnerability is tracked as CVE-2021-22205\u00a0and has a CVSS v3 score of 10.0, allowing an unauthenticated, remote attacker to execute arbitrary commands as the \u2018git\u2019 user (repository admin).\n\nThis vulnerability gives the remote attacker full access to the repository, including deleting, modifying, and stealing source code.\nSee Also: Complete Offensive Security and Ethical Hacking Course Exploitation in the wildHackers first started exploiting internet-facing GitLab servers in June 2021\u00a0to create new users and give them admin rights.\n\nThe actors used a working exploit published on GitHub\u00a0on June 4, 2021, allowing them to abuse the vulnerable ExifTool component.\n\nThe threat actors do not need to authenticate or use a CSRF token or even a valid HTTP endpoint to use the exploit.\n\nWith the exploitation continuing to this day, researchers from Rapid7 decided to look into the number of unpatched systems and determine the scope of the underlying problem.\nSee Also: All Windows versions impacted by new LPE zero-day vulnerability According to a report published by Rapid7, at least 50% of the 60,000 internet-facing GitLab installations they found are not patched against the critical RCE flaw fixed six months ago.\nMoreover, another 29% may or may not be vulnerable, as the analysts couldn\u2019t extract the version string for those servers.\n\nAdmins need to update to one of the following versions to patch the flaw:\n\n* 13.10.3\n* 13.9.6\n* 13.8.8\n\nAny versions earlier than that and down to 11.9 are vulnerable to exploitation whether you\u2019re using GitLab Enterprise Edition (EE) or GitLab Community Edition (CE).\nSee Also: Offensive Security Tool: ZipExec For more details on how to update GitLab, check out this dedicated portal.\n\nTo ensure that your GitLab instance isn\u2019t vulnerable to exploitation, you can check its response to POST requests that attempt to exploit ExifTool\u2019s mishandling of image files.\n\nThe patched versions still allow someone to reach out to ExifTool, but the response to the request should be a rejection\u00a0in the form of an HTTP 404 error.\nSee Also: Hacking stories \u2013 Operation Troy \u2013 How researchers linked the cyberattacks Source: www.bleepingcomputer.com (Click Link)Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/11/trojan-source-invisible-vulnerabilities-in-most-code-showcase_image-7-a-17833-90x90.jpg \u2018Trojan Source\u2019 attack method can hide bugs into open-source code1 day ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/11/ezgif.com-gif-maker-4-90x90.jpg Chaos ransomware targets gamers via fake Minecraft alt lists2 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/10/microsoft-zero-day-vulnerabilities-800x358-1-90x90.png All Windows versions impacted by new LPE zero-day vulnerability5 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/10/social_preview-scaled-90x90.jpg Sensitive data of 400,000 German students exposed by API flaw6 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/10/hacked-90x90.jpg Brutal WordPress plugin bug allows subscribers to wipe sites1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:10.846831Z"}