<?xml version="1.0" encoding="UTF-8"?><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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CUdefender &#187; vulnerability</title>
	<atom:link href="https://cudefender.com/category/vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>https://cudefender.com</link>
	<description>Credit Union Cyber Security Solutions</description>
	<lastBuildDate>Tue, 24 Feb 2015 18:51:22 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>POODLE Returns &#8211; Credit Unions Exposed</title>
		<link>https://cudefender.com/poodle-returns-credit-unions-exposed/</link>
		<comments>https://cudefender.com/poodle-returns-credit-unions-exposed/#comments</comments>
		<pubDate>Mon, 15 Dec 2014 14:18:51 +0000</pubDate>
		<dc:creator><![CDATA[Rob]]></dc:creator>
				<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://www.cudefender.com/?p=4280</guid>
		<description><![CDATA[<p>It&#8217;s been months since the POODLE SSL 3.0 vulnerability has been discovered and many credit unions and even large banks are still trying to figure out how to mitigate the risk. Now, as of December 8th, 2014, a new twist on POODLE reveals even more risk. A cursory review using a SSL/TLS scanning tool indicates that the [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://cudefender.com/poodle-returns-credit-unions-exposed/">POODLE Returns &#8211; Credit Unions Exposed</a> appeared first on <a rel="nofollow" href="https://cudefender.com">CUdefender</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>It&#8217;s been months since the POODLE SSL 3.0 vulnerability has been discovered and many credit unions and even large banks are still trying to figure out how to mitigate the risk. Now, as of December 8th, 2014, a new twist on POODLE reveals even more risk. A cursory review using a SSL/TLS scanning tool indicates that the Web sites for some of the world’s largest financial institutions are vulnerable to the new POODLE bug, including Bank of America, Chase.com, Citibank, HSBC, Suntrust — as well as many credit unions across the nation. This is a serious risk.</p>
<p>Firstly, if you&#8217;re reading this as a <strong>CUdefender customer</strong> using our security services, <strong>you are already protected</strong>. But, there is still some information you may still like to know.</p>
<p><strong>What is POODLE?</strong></p>
<p>“POODLE,” an acronym for a serious security flaw in a specific version (version 3.0) of <a title="http://en.wikipedia.org/wiki/Transport_Layer_Security" href="http://en.wikipedia.org/wiki/Transport_Layer_Security" target="_blank">Secure Sockets Layer</a> (SSL), the technology that most web sites use to protect the privacy and security of communications with customers.</p>
<p><strong>What systems could be affected?</strong></p>
<p>Any web browser accessible system supporting SSL 3.0 and certain versions of TLS.</p>
<p><strong>What are the security consequences?</strong></p>
<p>POODLE can potentially lead to exposure of personal data such as email addresses, passwords, and credit card numbers—the very things SSL was designed to protect. Basically, any data sent of a vulnerable encrypted connection could be at risk.</p>
<p><strong>How can our credit union protect against POODLE?</strong></p>
<p>According to <a title="https://www.us-cert.gov/ncas/alerts/TA14-290A" href="https://www.us-cert.gov/ncas/alerts/TA14-290A" target="_blank">an advisory</a> from the <strong>U.S. Computer Emergency Readiness Team</strong> (US-CERT), a partnership run in conjunction with the U.S. Department of Homeland Security, although there is currently no fix for the vulnerability SSL 3.0 itself, disabling SSL 3.0 support in Web applications is the most viable solution currently available. US-CERT notes that some of the same researchers who <a title="https://www.imperialviolet.org/2014/12/08/poodleagain.html" href="https://www.imperialviolet.org/2014/12/08/poodleagain.html" target="_blank">discovered</a> the Poodle vulnerability also developed a fix for the TLS-related issues.</p>
<p><strong>Non-CUdefender users:</strong></p>
<p>1. Scan your web endpoints using a good SSL/TLS scanning tool to determine vulnerable systems (many free scanning tools exist).<br />
2. Disable SSL 3.0 on any web exposed system including websites, webmail, remote access gateways, online account opening tools, etc.</p>
<p><strong>CUdefender users:</strong></p>
<p>1. CUdefender has immediately removed support for POODLE-vulnerable CBC ciphers. CUdefender customers are not susceptible to the POODLE vulnerability for protected endpoints.</p>
<p>For more information on how CUdefender can protect your credit union, please visit http://www.cudefender.com or contact us now at 888-632-4339.</p>
<p>The post <a rel="nofollow" href="https://cudefender.com/poodle-returns-credit-unions-exposed/">POODLE Returns &#8211; Credit Unions Exposed</a> appeared first on <a rel="nofollow" href="https://cudefender.com">CUdefender</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://cudefender.com/poodle-returns-credit-unions-exposed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CUdefender Protects Credit Unions Against &#8220;Shellshock&#8221; Vulnerability</title>
		<link>https://cudefender.com/cudefender-protects-against-shellshock-vulnerability/</link>
		<comments>https://cudefender.com/cudefender-protects-against-shellshock-vulnerability/#comments</comments>
		<pubDate>Fri, 26 Sep 2014 01:27:08 +0000</pubDate>
		<dc:creator><![CDATA[Rob]]></dc:creator>
				<category><![CDATA[vulnerability]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.cudefender.com/?p=4093</guid>
		<description><![CDATA[<p>Yesterday, a security researcher released the details of a major security vulnerability in Bash, a.k.a. Bourne-Again Shell, a popular software utility. The vulnerability, known as Shellshock, will be a serious problem for many Linux, Unix, and Mac OS X users. In order to protect our Credit Union customers from being affected by Shellshock, CUdefender has proactively [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://cudefender.com/cudefender-protects-against-shellshock-vulnerability/">CUdefender Protects Credit Unions Against &#8220;Shellshock&#8221; Vulnerability</a> appeared first on <a rel="nofollow" href="https://cudefender.com">CUdefender</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>Yesterday, a <a title="security researcher" href="http://stephane.chazelas.free.fr/">security researcher</a> released the details of a major security vulnerability in Bash, a.k.a. Bourne-Again Shell, a popular software utility.</p>
<p>The vulnerability, known as Shellshock, will be a serious problem for many Linux, Unix, and Mac OS X users.</p>
<p>In order to protect our Credit Union customers from being affected by Shellshock, CUdefender has proactively updated its Web Application Firewall (WAF) rules to block the vulnerability.</p>
<p>Our implemented security rules work in multiple stages to ensure that Shellshock cannot be exploited on systems protected by CUdefenders’s WAF.</p>
<p>As a best practice, administrators of any systems running Bash should patch their systems as soon as patches for their distributions are available, even if those systems are already protected by CUdefender. Mjor Linux distributions such as Redhat, have already released patches.</p>
<p>Some vendors and third parties have already gone as far as creating simple diagnostic tools which can be run after patching to make sure that the vulnerability is closed and unexploitable on your system.</p>
<p>Technical details for Shellshock and affected versions for this vulnerability can be found in the National Vulnerability Database using the ID #’s <a title="CVE-2014-6271" href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271">CVE-2014-6271</a> and <a title="CVE-2014-7169" href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-7169">CVE-2014-7169</a>.</p>
<p>The post <a rel="nofollow" href="https://cudefender.com/cudefender-protects-against-shellshock-vulnerability/">CUdefender Protects Credit Unions Against &#8220;Shellshock&#8221; Vulnerability</a> appeared first on <a rel="nofollow" href="https://cudefender.com">CUdefender</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://cudefender.com/cudefender-protects-against-shellshock-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.552 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2025-12-14 05:51:10 -->
