<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2-bleeding" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>cryptoresync</title>
	<link>http://cryptoresync.com</link>
	<description>A blog devoted to information system security, privacy and other similar topics</description>
	<pubDate>Wed, 30 Jan 2008 14:43:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2-bleeding</generator>
	<language>en</language>
			<item>
		<title>Microsoft&#8217;s &#8220;Black&#8221; Patch Tuesday</title>
		<link>http://cryptoresync.com/2007/01/11/microsofts-black-patch-tuesday/</link>
		<comments>http://cryptoresync.com/2007/01/11/microsofts-black-patch-tuesday/#comments</comments>
		<pubDate>Thu, 11 Jan 2007 12:07:27 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Updates</dc:subject>
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2007/01/11/microsofts-black-patch-tuesday/</guid>
		<description><![CDATA[A new year and a new set of Microsoft security updates no thanks to another fun installment of Microsoft â€œPatch Tuesday.â€ This month we see Microsoft offering an &#8220;important&#8221; fix for a multilingual version of Office 2003, a critical Outlook patch, a critical Excel patch and lastly, a critical vector markup language patch.
The following is [...]]]></description>
			<content:encoded><![CDATA[<p>A new year and a new set of Microsoft security updates no thanks to another fun installment of Microsoft â€œPatch Tuesday.â€ This month we see Microsoft offering an &#8220;important&#8221; fix for a multilingual version of Office 2003, a critical Outlook patch, a critical Excel patch and lastly, a critical vector markup language patch.</p>
<p>The following is a list of what new goodies our faithful friend, Microsoft, has removed from their big bag of presents:</p>
<blockquote><p>
<a href="http://www.microsoft.com/technet/security/Bulletin/MS07-001.mspx">MS07-001: Vulnerability in Microsoft Office 2003 Brazilian Portuguese Grammar Checker Could Allow Remote Code Execution</a>.<br />
KB Number: 921585<br />
Severity: Important</p>
<p><a href="http://www.microsoft.com/technet/security/Bulletin/MS07-002.mspx">MS07-002: Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution</a>.<br />
KB Number: 927198<br />
Severity: <strong>Critical</strong></p>
<p><a href="http://www.microsoft.com/technet/security/Bulletin/MS07-003.mspx">MS07-003: Vulnerabilities in Microsoft Outlook Could Allow Remote Code Execution</a>.<br />
KB Number: 925938<br />
Severity: <strong>Critical</strong></p>
<p><a href="http://www.microsoft.com/technet/security/Bulletin/MS07-004.mspx">MS07-004: Vulnerability in Vector Markup Language Could Allow Remote Code Execution</a>.<br />
KB Number: 929969<br />
Severity: <strong>Critical</strong>
</p></blockquote>
<p>I highly recomment that these patches be installed once they have been delivered to you via Microsoftâ€™s automatic update service. If, for whatever reason, you do not see them show up anytime soon then I strongly recommend that you force-check for new updates. Once prompted to install these security patches then do so immediately.</p>
<p>What will February have in store for Windows users across the world? Only time will tell!</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2007/01/11/microsofts-black-patch-tuesday/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Wordpress Unspecified Vulnerability</title>
		<link>http://cryptoresync.com/2007/01/08/wordpress-unspecified-vulnerability/</link>
		<comments>http://cryptoresync.com/2007/01/08/wordpress-unspecified-vulnerability/#comments</comments>
		<pubDate>Mon, 08 Jan 2007 00:49:32 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2007/01/08/wordpress-unspecified-vulnerability/</guid>
		<description><![CDATA[Secunia is reporting that an unspecified vulnerability has been found in Wordpress. This, along with a user account enumeration weakness, is the latest security issue to affect the highly popular open-source blogging platform.
The unspecified vulnerability affects all versions prior to 2.0.6 whereas the user account enumeration weakness has been confirmed to only affect 2.0.5. Other [...]]]></description>
			<content:encoded><![CDATA[<p>Secunia is reporting that an <a href="http://secunia.com/advisories/23595/">unspecified vulnerability</a> has been found in <a href="http://wordpress.org/">Wordpress</a>. This, along with a <a href="http://secunia.com/advisories/23621/">user account enumeration weakness</a>, is the latest security issue to affect the highly popular open-source blogging platform.</p>
<p>The unspecified vulnerability affects all versions prior to 2.0.6 whereas the user account enumeration weakness has been confirmed to only affect 2.0.5. Other releases <em>may</em> be affected but have yet to be validated.</p>
<p>In order to mitigate these issues it is highly recommended that users <a href="http://wordpress.org/development/2007/01/wordpress-206/">upgrade</a> to Wordpress 2.0.6. It is always recommended to upgrade when critical security issues are located in products that are currently in use.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2007/01/08/wordpress-unspecified-vulnerability/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Click Fraud and the Problem of Authenticating People</title>
		<link>http://cryptoresync.com/2006/07/13/click-fraud-and-the-problem-of-authenticating-people/</link>
		<comments>http://cryptoresync.com/2006/07/13/click-fraud-and-the-problem-of-authenticating-people/#comments</comments>
		<pubDate>Thu, 13 Jul 2006 12:39:08 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/13/click-fraud-and-the-problem-of-authenticating-people/</guid>
		<description><![CDATA[Once again Bruce Schneier hits the nail on head with his exceptionally insightful article about click fraud and the problem of authenticating people. With his usual eloquence, and his ability to get right to the point without useless prose, Schneier explains why solving the click fraud problem is imperative.
Googles $6 billion-a-year advertising business is at [...]]]></description>
			<content:encoded><![CDATA[<p>Once again Bruce Schneier hits the nail on head with his exceptionally insightful article about <a href="http://www.schneier.com/blog/archives/2006/07/click_fraud_and.html">click fraud and the problem of authenticating people</a>. With his usual eloquence, and his ability to get right to the point without useless prose, Schneier explains why solving the click fraud problem is imperative.</p>
<blockquote><p>Googles $6 billion-a-year advertising business is at risk because it cant be sure that anyone is looking at its ads. The problem is called click fraud, and it comes in two basic flavors.</p></blockquote>
<blockquote><p>Google is testing a new advertising model to deal with click fraud: cost-per-action ads. Advertisers don&#8217;t pay unless the customer performs a certain action: buys a product, fills out a survey, whatever. It&#8217;s a hard model to make work &#8212; Google would become more of a partner in the final sale instead of an indifferent displayer of advertising &#8212; but it&#8217;s the right security response to click fraud: Change the rules of the game so that click fraud doesn&#8217;t matter.</p>
<p>That&#8217;s how to solve a security problem.</p></blockquote>
<p>Google is definitely taking the right path on this one. The wise words, from an even wiser security expert, should not be ignored.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/13/click-fraud-and-the-problem-of-authenticating-people/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Citibank Phish Spoofs 2-Factor Authentication</title>
		<link>http://cryptoresync.com/2006/07/11/citibank-phish-spoofs-2-factor-authentication/</link>
		<comments>http://cryptoresync.com/2006/07/11/citibank-phish-spoofs-2-factor-authentication/#comments</comments>
		<pubDate>Tue, 11 Jul 2006 10:21:49 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/11/citibank-phish-spoofs-2-factor-authentication/</guid>
		<description><![CDATA[A new phishing site was recently located, which ended up breaking the two-factor authentication in use by Citibank by conducting a man in the middle attack. Two-factor authentication is any authentication protocol that requires two independent ways to establish identity and privileges. By necessitating the need to have a combination of something you know (i.e. [...]]]></description>
			<content:encoded><![CDATA[<p>A new phishing site was recently located, which ended up <a href="http://blog.washingtonpost.com/securityfix/2006/07/citibank_phish_spoofs_2factor_1.html">breaking the two-factor authentication in use by Citibank</a> by conducting a man in the middle attack. Two-factor authentication is any authentication protocol that requires two independent ways to establish identity and privileges. By necessitating the need to have a combination of something you know (i.e. username and password), something you have (i.e. a token or smart card) or something you are (i.e. biometrics), security is greatly enhanced. This contrasts with traditional password authentication, which requires only one factor (knowledge of a password) in order to gain access to a system.</p>
<blockquote><p>Security experts have long touted the need for financial Web sites to move beyond mere passwords and implement so-called &#8220;two-factor authentication&#8221; &#8212; the second factor being something the user has in their physical possession like an access card &#8212; as the answer to protecting customers from phishing attacks that use phony e-mails and bogus Web sites to trick users into forking over their personal and financial data.</p></blockquote>
<p>This attack was fairly complex and done exceptionally well. Most security experts would have been able to spot it immediately, however the lay person might not know any better. Just goes to show that just because something is two-factor does not automatically mean that the entirety of its security design is better than if it were single-factor.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/11/citibank-phish-spoofs-2-factor-authentication/feed/</wfw:commentRss>
		</item>
		<item>
		<title>More on VA Data Theft</title>
		<link>http://cryptoresync.com/2006/07/07/more-on-va-data-theft/</link>
		<comments>http://cryptoresync.com/2006/07/07/more-on-va-data-theft/#comments</comments>
		<pubDate>Fri, 07 Jul 2006 11:31:21 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject><dc:subject>security</dc:subject><dc:subject>theft</dc:subject><dc:subject>va</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/07/more-on-va-data-theft/</guid>
		<description><![CDATA[27B Stroke 6 as some more on the VA data theft, which contained an immense amount of information on US veterans and active duty military.  This whole story is turning in to something very interesting. More specifically, a test case on how not to handle stolen sensitive material.
The FBI has done some forensic work [...]]]></description>
			<content:encoded><![CDATA[<p>27B Stroke 6 as some <a href="http://blog.wired.com/27BStroke6/index.blog?entry_id=1515757">more on the VA data theft</a>, which contained an immense amount of information on US veterans and active duty military.  This whole story is turning in to something very interesting. More specifically, a test case on how not to handle stolen sensitive material.</p>
<blockquote><p>The FBI has done some forensic work on the laptop and says it can&#8217;t find any evidence that the data was accessed.  InfoWorld&#8217;s Robert Grimes chimes in to say, Rumsfeld style, that the absence of evidence is not the evidence of absence, since any fool could have simply cloned the disk and then accessed the database on the cloned disk.</p>
<p>Now, there&#8217;s also some back in forth in the VA about whether the data analyst was authorized to take the data home.  The analyst, who has been fired, says he has a letter authorizing him to take the data home, while the VA says the letter is for a different computer.</p></blockquote>
<p>What really concerns me is this: why was this analyst working with social security numbers on a laptop, rather than in the office while connected to the network? I can not, for the life of me, come up with a good reason for why this analyst was doing what he was doing, with the data that ultimately ended up stolen.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/07/more-on-va-data-theft/feed/</wfw:commentRss>
		</item>
		<item>
		<title>MacBook Pro Biometrics</title>
		<link>http://cryptoresync.com/2006/07/07/macbook-pro-biometrics/</link>
		<comments>http://cryptoresync.com/2006/07/07/macbook-pro-biometrics/#comments</comments>
		<pubDate>Fri, 07 Jul 2006 11:27:29 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/07/macbook-pro-biometrics/</guid>
		<description><![CDATA[This guy retrofitted his MacBook Pro with a biometric scanner. It has to be the worlds first. Very neat way to engage added security for a notebook.
]]></description>
			<content:encoded><![CDATA[<p>This guy <a href="http://edahc.blogspot.com/2006/06/macbook-pro-biometrics.html">retrofitted his MacBook Pro with a biometric scanner</a>. It has to be the worlds first. Very neat way to engage added security for a notebook.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/07/macbook-pro-biometrics/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Microsoft Patch Tuesday Will Offer 7 Security Patches</title>
		<link>http://cryptoresync.com/2006/07/07/microsoft-patch-tuesday-will-offer-7-security-patches/</link>
		<comments>http://cryptoresync.com/2006/07/07/microsoft-patch-tuesday-will-offer-7-security-patches/#comments</comments>
		<pubDate>Fri, 07 Jul 2006 10:44:11 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject><dc:subject>microsoft</dc:subject><dc:subject>patches</dc:subject><dc:subject>security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/07/microsoft-patch-tuesday-will-offer-7-security-patches/</guid>
		<description><![CDATA[The upcoming patch Tuesday from Microsoft will offer 7 security patches to reconcile vulnerabilities found in their widely used software.
Although Microsoft does not disclose in advance what flaws are to be patched, two vulnerabilities in Excel are likely to be among the fixes. One issue relates to maliciously crafted spreadsheet files that could lead to [...]]]></description>
			<content:encoded><![CDATA[<p>The upcoming patch Tuesday from Microsoft <a href="http://www.betanews.com/article/Microsoft_to_Issue_7_Security_Patches/1152209008">will offer 7 security patches</a> to reconcile vulnerabilities found in their widely used software.</p>
<blockquote><p>Although Microsoft does not disclose in advance what flaws are to be patched, two vulnerabilities in Excel are likely to be among the fixes. One issue relates to maliciously crafted spreadsheet files that could lead to a full system compromise, while the other relates to hyperlinks in Excel documents.</p>
<p>Two security flaws affecting Internet Explorer were also reported last week, including a cross-site scripting issue where an attacker could view information in an open browser window from another that is visiting a malicious site.</p></blockquote>
<p>As usual, Internet Explorer is being fixed yet again. For the second month straight Excel will receive some patch love among a few others that we are not yet aware of. If you are a corporate system administrator then ensure you test these patches on a closed network before deploying throughout your enterprise.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/07/microsoft-patch-tuesday-will-offer-7-security-patches/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Windows Vista Gets ActiveX Installer Service</title>
		<link>http://cryptoresync.com/2006/07/06/windows-vista-gets-activex-installer-service/</link>
		<comments>http://cryptoresync.com/2006/07/06/windows-vista-gets-activex-installer-service/#comments</comments>
		<pubDate>Thu, 06 Jul 2006 11:14:27 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject><dc:subject>design</dc:subject><dc:subject>security</dc:subject><dc:subject>windows</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/07/06/windows-vista-gets-activex-installer-service/</guid>
		<description><![CDATA[Once again, Microsoft is bowing to pressure from businesses rather than thinking of possible security ramifications of the features they add to Windows Vista. This time Windows Vista gets an ActiveX installer service so that the controls can be installed on client workstations regardless of the permissions of the user logged in.
The new feature, called [...]]]></description>
			<content:encoded><![CDATA[<p>Once again, Microsoft is bowing to pressure from businesses rather than thinking of possible security ramifications of the features they add to Windows Vista. This time <a href="http://www.eweek.com/article2/0,1759,1979231,00.asp?kc=EWRSS03119TX1K0000594">Windows Vista gets an ActiveX installer service</a> so that the controls can be installed on client workstations regardless of the permissions of the user logged in.</p>
<blockquote><p>The new feature, called ActiveX Installer Service, will be fitted into the next public release of Vista to provide a way for enterprises to cope with the UAC (User Account Control) security mechanism.</p>
<p>UAC, formerly known as LUA (Limited User Account), is enabled by default in Vista to separate Standard User privileges from those that require admin rights to harden the operating system against malware and malicious hacker attacks.</p>
<p>However, because UAC will block the installation of ActiveX controls on Standard User systems, enterprise applications that use the technology will encounter breakages. ActiveX controls are objects used to enhance a user&#8217;s interaction with an application.</p></blockquote>
<p>This sounds like an exploit that many will be salivating to take control of. While it remains to be seen just how vulnerable this &#8220;feature&#8221; is, the base description certainly leaves a lot to be desired. How long before a privilege escalation exploit is released?</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/07/06/windows-vista-gets-activex-installer-service/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Catawba County Schools Plays &#8220;Blame Game&#8221;</title>
		<link>http://cryptoresync.com/2006/06/26/catawba-county-schools-plays-blame-game/</link>
		<comments>http://cryptoresync.com/2006/06/26/catawba-county-schools-plays-blame-game/#comments</comments>
		<pubDate>Mon, 26 Jun 2006 11:40:08 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Security</dc:subject><dc:subject>google</dc:subject><dc:subject>security</dc:subject><dc:subject>web</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/06/26/catawba-county-schools-plays-blame-game/</guid>
		<description><![CDATA[The Catawba County Schools is playing the blame game rather than owning up to operator error on behalf of their own employees. The school district somehow convinved a judge to issue an injunction against Google for allegedly posting names, social security numbers and grades of 619 students.
They school district claims that Google somehow trespassed on [...]]]></description>
			<content:encoded><![CDATA[<p>The Catawba County Schools is playing the <a href="http://www.journalnow.com/servlet/Satellite?pagename=WSJ/MGArticle/WSJ_BasicArticle&#038;c=MGArticle&#038;cid=1149188715340&#038;path=!localnews!newsvine&#038;s=1037645509099">blame game</a> rather than owning up to operator error on behalf of their own employees. The school district somehow convinved a judge to issue an injunction against Google for allegedly posting names, social security numbers and grades of 619 students.</p>
<p>They school district claims that Google somehow trespassed on their server and made information publicly available. There is very little information about this incident being publicly released, however the following statement really caught my attention:</p>
<blockquote><p>&#8220;One of the students on the list had a presence on the Web,&#8221; she said. &#8220;In Googleâ€™s effort to get information on her, one of its spiders latched onto her name in this document. We were not aware that password-protected sites are set up like that. To our knowledge, Google could only cache unsecure information that did not require a password or username.&#8221;</p></blockquote>
<p>Based on reading the statement by the district I can only surmise that they have incompetent system administrators working on their web server. It is common knowledge by those in the industry that if information is posted on a publicly accessible web site then it can be spidered and indexed by Google. If the information is <em>properly protected</em> then there is no way for Google&#8217;s spider to crawl the documents, therefore they will not be included in their index.</p>
<p>Sadly, it appears that nobody is willing to own up and tell the school district that they made a mistake. Taxpayer dollars will be wasted on a baseless lawsuit that could have been avoided if 1) the district hired competent system administrators and 2) the employees properly briefed their supervisors on their own mistakes.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/06/26/catawba-county-schools-plays-blame-game/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Microsoft Acknowledges Excel Vulnerability</title>
		<link>http://cryptoresync.com/2006/06/20/microsoft-acknowledges-excel-vulnerability/</link>
		<comments>http://cryptoresync.com/2006/06/20/microsoft-acknowledges-excel-vulnerability/#comments</comments>
		<pubDate>Tue, 20 Jun 2006 08:43:19 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
		
	<dc:subject>Exploits</dc:subject>
	<dc:subject>Security</dc:subject>
		<guid isPermaLink="false">http://cryptoresync.com/2006/06/20/microsoft-acknowledges-excel-vulnerability/</guid>
		<description><![CDATA[Microsoft issued a security advisory  for an Excel vulnerability that I recently wrote about. The company acknowledged reports of the exploit but has not yet determined the cause, or any fix action as of yet.
Microsoft is investigating new public reports of limited â€œzero-dayâ€ attacks using a vulnerability in Microsoft Excel 2003, Excel Viewer 2003, [...]]]></description>
			<content:encoded><![CDATA[<p>Microsoft <a href="http://www.microsoft.com/technet/security/advisory/921365.mspx">issued a security advisory </a> for an <a href="http://cryptoresync.com/2006/06/16/new-microsoft-excel-vulnerability-found/">Excel vulnerability</a> that I recently wrote about. The company acknowledged reports of the exploit but has not yet determined the cause, or any fix action as of yet.</p>
<blockquote><p>Microsoft is investigating new public reports of limited â€œzero-dayâ€ attacks using a vulnerability in Microsoft Excel 2003, Excel Viewer 2003, Excel 2002, Excel 2000, Microsoft Excel 2004 for Mac, and Microsoft Excel v. X for Mac. In order for this attack to be carried out, a user must first open a malicious Excel file attached to an e-mail or otherwise provided to them by an attacker.</p></blockquote>
<p>In order to avoid the possibility of being compromised by this vulnerability just do not open attachments from untrusted, unreliable authors. This is a best practice that should be followed daily. If you are already weary about opening attachments from unknown senders then you are on the right track.</p>
]]></content:encoded>
			<wfw:commentRss>http://cryptoresync.com/2006/06/20/microsoft-acknowledges-excel-vulnerability/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
