{"uuid": "85422738-e61e-450a-85e0-199155471ccf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-41773", "type": "seen", "source": "https://t.me/hacking_Attack/29560", "content": "Installation\n- git clone https://github.com/HightechSec/scarce-apache2\n- cd scarce-apache2\n- bash scarce.sh\nor you can install in your system like this- git clone https://github.com/HightechSec/scarce-apache2\n- cd scarce-apache2\n- sudo cp scarce.sh /usr/bin/scarce &amp;&amp; sudo chmod +x /usr/bin/scarce\n- $ scarce\n\nUsage\nMenu's Menu 1 is for scanning LFI Vulnerability (https://www.kitploit.com/search/label/LFI%20Vulnerability) from a provided file that contains the list of the target url or a provided single target url.Menu 2 is for scanning RCE Vulnerability from a provided file that contains the list of the target url or a provided single target url.Menu 3 is for Executing RCE from a provided single target url. This will work for the Maybe Vuln Results or sometimes with a 500 Error Response.URL Format Use http:// like http://example.com or https:// like https://example.com for the url formatting at Single Target usagesFor Url or IP that has been provided from a List, Don't Use the URL Formatting like eg: https://target.com (https://target.com/)http://hackerone.com (http://hackerone.com/)https://bugcrowd.com (https://bugcrowd.com/)\nRequirements\ncurlbashgit\nCredits\nThanks to:CVE-2021-41773 Reproduced (https://twitter.com/ptswarm/status/1445376079548624899) by @ptswarm (https://twitter.com/ptswarm)Executing RCE in CVE-2021-41773 (https://twitter.com/hackerfantastic/status/1445531829985968137) by @hackerfantastic (https://twitter.com/hackerfantastic)Removing 5xx Error when Running RCE (https://twitter.com/lukejahnke/status/1445560511270064138) by @lukejahnke (https://twitter.com/lukejahnke)\n\nDownload Scarce-Apache2 (https://github.com/HightechSec/scarce-apache2)\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:10.777700Z"}