<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"

	>
<channel>
	<title>Comments on: TimThumb.php Vulnerability Scans</title>
	<atom:link href="/2011/09/09/timthumb-php-vulnerability-scans/feed/" rel="self" type="application/rss+xml" />
	<link>/2011/09/09/timthumb-php-vulnerability-scans/</link>
	<description>Tips and tricks to get technology to work for you, by Michael Boyd Clark</description>
	<lastBuildDate>Sat, 20 Feb 2016 14:14:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: JeffM</title>
		<link>/2011/09/09/timthumb-php-vulnerability-scans/comment-page-1/#comment-20407</link>
		<dc:creator><![CDATA[JeffM]]></dc:creator>
		<pubDate>Wed, 21 Sep 2011 14:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmike.com/?p=1468#comment-20407</guid>
		<description><![CDATA[I also started getting hit by these scans about a month ago. It began with /wp-content/plugins scans, and this week it&#039;s targetting /wp-content/themes.

It&#039;s looking for other scripts too, like thumb.php, cropper.php, img.php and getimg.php.
My site doesn&#039;t host any of those scripts, but when it gets scanned I notice there&#039;s always a &#039;blank&#039; referrer in the request. I&#039;d have expected a referrer, at least.

This .htaccess rule is working fine for me:


	RewriteEngine On
	RewriteBase /
	RewriteCond %{HTTP_REFERER} ^-?$ # if referrer empty (or faked empty)
	RewriteCond %{REQUEST_URI} ((tim)?thumb&#124;cropper&#124;img&#124;getimg)\.php$ [NC] # deny the request
	RewriteRule .* - [F]


It catches all IPs (present and future, hopefully). I&#039;ve tried a 301 back to the REMOTE_ADDRESS but it made no diff, they just keep coming.]]></description>
		<content:encoded><![CDATA[<p>I also started getting hit by these scans about a month ago. It began with /wp-content/plugins scans, and this week it&#8217;s targetting /wp-content/themes.</p>
<p>It&#8217;s looking for other scripts too, like thumb.php, cropper.php, img.php and getimg.php.<br />
My site doesn&#8217;t host any of those scripts, but when it gets scanned I notice there&#8217;s always a &#8216;blank&#8217; referrer in the request. I&#8217;d have expected a referrer, at least.</p>
<p>This .htaccess rule is working fine for me:</p>
<p>	RewriteEngine On<br />
	RewriteBase /<br />
	RewriteCond %{HTTP_REFERER} ^-?$ # if referrer empty (or faked empty)<br />
	RewriteCond %{REQUEST_URI} ((tim)?thumb|cropper|img|getimg)\.php$ [NC] # deny the request<br />
	RewriteRule .* &#8211; [F]</p>
<p>It catches all IPs (present and future, hopefully). I&#8217;ve tried a 301 back to the REMOTE_ADDRESS but it made no diff, they just keep coming.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
