<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<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:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Microsoft on Untrusted Network</title>
    <link>https://untrustednetwork.net/en/tag/microsoft/</link>
    <description>Recent content in Microsoft on Untrusted Network</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&amp;copy; Jan Kopriva 2015 - {year}</copyright>
    <lastBuildDate>Mon, 09 Aug 2021 12:25:00 +0200</lastBuildDate>
    <sy:updatePeriod>weekly</sy:updatePeriod>
    <sy:updateFrequency>weekly</sy:updateFrequency>
    
        <atom:link href="https://untrustednetwork.net/en/tag/microsoft/index.xml" rel="self" type="application/rss+xml" />
    
    
    

      
      <item>
        <title>SANS ISC Diary - ProxyShell - how many Exchange servers are affected and where are they?</title>
        <link>https://untrustednetwork.net/en/2021/08/09/proxyshell/</link>
        <pubDate>Mon, 09 Aug 2021 12:25:00 +0200</pubDate>
        
        <atom:modified>Mon, 09 Aug 2021 12:25:00 +0200</atom:modified>
        <guid>https://untrustednetwork.net/en/2021/08/09/proxyshell/</guid>
        <description>A new Diary of mine was published today on the SANS Internet Storm Center website. In this one, we&amp;rsquo;ll take a look at the number of Exchange serveres vulnerable to the ProxyShell attack&amp;hellip;</description>
        <content:encoded>&lt;p&gt;A new &lt;a href=&#34;https://isc.sans.edu/diary/27732&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt; website. In this one, we&amp;rsquo;ll take a look at the number of Exchange serveres vulnerable to the ProxyShell attack&amp;hellip;&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>Vulnerability</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Exchange</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2021</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>SANS ISC Diary - SMBGhost - the critical vulnerability many seem to have forgotten to patch</title>
        <link>https://untrustednetwork.net/en/2020/10/28/sans-isc-diary-smbghost-the-critical-vulnerability-many-seem-to-have-forgotten-to-patch/</link>
        <pubDate>Wed, 28 Oct 2020 11:00:00 +0200</pubDate>
        
        <atom:modified>Wed, 28 Oct 2020 11:00:00 +0200</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/10/28/sans-isc-diary-smbghost-the-critical-vulnerability-many-seem-to-have-forgotten-to-patch/</guid>
        <description>A Diary of mine was published today on the SANS Internet Storm Center. In this one, we take a look at the concerning number of machines connected to the internet, that are still not patched for the critical SMBGhost vulnerability.</description>
        <content:encoded>&lt;p&gt;A &lt;a href=&#34;https://isc.sans.edu/forums/diary/SMBGhost+the+critical+vulnerability+many+seem+to+have+forgotten+to+patch/26732/&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt;. In this one, we take a look at the concerning number of machines connected to the internet, that are still not patched for the critical SMBGhost vulnerability.&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>SMBGhost</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Vulnerability</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2020</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>SANS ISC Diary - Using Shell Links as zero-touch downloaders and to initiate network connections</title>
        <link>https://untrustednetwork.net/en/2020/06/24/sans-isc-diary-using-shell-links-as-zero-touch-downloaders-and-to-initiate-network-connections/</link>
        <pubDate>Wed, 24 Jun 2020 09:45:00 +0200</pubDate>
        
        <atom:modified>Wed, 24 Jun 2020 09:45:00 +0200</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/06/24/sans-isc-diary-using-shell-links-as-zero-touch-downloaders-and-to-initiate-network-connections/</guid>
        <description>A Diary of mine was published today on the SANS Internet Storm Center. In this one, we take a look at a weakness handling of LNK files in Windows, through which one may force the OS to download an arbitrary file from a remote server any time the shortcut file is displayed.</description>
        <content:encoded>&lt;p&gt;A &lt;a href=&#34;https://isc.sans.edu/forums/diary/Using+Shell+Links+as+zerotouch+downloaders+and+to+initiate+network+connections/26276/&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt;. In this one, we take a look at a weakness handling of LNK files in Windows, through which one may force the OS to download an arbitrary file from a remote server any time the shortcut file is displayed.&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>LNK</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Windows</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2020</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>SANS ISC Diary - Crashing explorer.exe with(out) a click</title>
        <link>https://untrustednetwork.net/en/2020/03/30/sans-isc-diary-crashing-explorer.exe-without-a-click/</link>
        <pubDate>Mon, 30 Mar 2020 07:55:00 +0100</pubDate>
        
        <atom:modified>Mon, 30 Mar 2020 07:55:00 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/03/30/sans-isc-diary-crashing-explorer.exe-without-a-click/</guid>
        <description>A Diary of mine was published today on the SANS Internet Storm Center. In this one, we take a look at a vulnerability in the way Windows handles self-referential links, which makes it possible to use specially crafted URL and LNK files to crash Explorer.</description>
        <content:encoded>&lt;p&gt;A &lt;a href=&#34;https://isc.sans.edu/forums/diary/Crashing+explorerexe+without+a+click/25966/&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt;. In this one, we take a look at a vulnerability in the way Windows handles self-referential links, which makes it possible to use specially crafted URL and LNK files to crash Explorer.&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Vulnerability</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Post-exploitation</category>
            
          
            
              <category>Red teaming</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2020</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>CrisisCon - Breaking Windows</title>
        <link>https://untrustednetwork.net/en/2020/03/28/crisiscon-breaking-windows/</link>
        <pubDate>Sat, 28 Mar 2020 09:15:00 +0100</pubDate>
        
        <atom:modified>Sat, 28 Mar 2020 09:15:00 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/03/28/crisiscon-breaking-windows/</guid>
        <description>Videos of all presentations from last weeks CrisisCon are now accessible on Youtube. Among them is my own talk on known unpatched vulnerabilities and weaknesses in Windows.
If you couldn&amp;rsquo;t make it to the online conference, I recommend you at least go through some of the recordings as couple of the talks were quite interesting.</description>
        <content:encoded>&lt;p&gt;Videos of all presentations from last weeks &lt;a href=&#34;https://crisiscon.net/&#34;&gt;CrisisCon&lt;/a&gt; are now accessible on &lt;a href=&#34;https://www.youtube.com/channel/UCaHzh5ByE44ucW-gAmOReeQ&#34;&gt;Youtube&lt;/a&gt;. Among them is my own talk on &lt;a href=&#34;https://www.youtube.com/watch?v=m_FwZE-5QGE&#34;&gt;known unpatched vulnerabilities and weaknesses in Windows&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you couldn&amp;rsquo;t make it to the online conference, I recommend you at least go through some of the recordings as couple of the talks were quite interesting.&lt;/p&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/icons/microphone.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>Windows</category>
            
          
            
              <category>Vulnerability</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Conference</category>
            
          
        
        
          
            
              <category>2020</category>
            
          
            
              <category>Talks</category>
            
          
        
        
      </item>
      
      <item>
        <title>SANS ISC Diary - Desktop.ini as a post-exploitation tool</title>
        <link>https://untrustednetwork.net/en/2020/03/16/sans-isc-diary-desktop.ini-as-a-post-exploitation-tool/</link>
        <pubDate>Mon, 16 Mar 2020 07:55:00 +0100</pubDate>
        
        <atom:modified>Mon, 16 Mar 2020 07:55:00 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/03/16/sans-isc-diary-desktop.ini-as-a-post-exploitation-tool/</guid>
        <description>A Diary of mine was published today on the SANS Internet Storm Center. In this one, we take a look at a vulnerability in the way Windows handles desktop.ini files, which makes it possible to use them as an interesting post-exploitation tool.
UPDATE 27. 5. 2020: I put together a shor video demonstrating the vulnerabiltiy while preparing materials for SANSFIRE 2020. You may find it here.</description>
        <content:encoded>&lt;p&gt;A &lt;a href=&#34;https://isc.sans.edu/forums/diary/Desktopini+as+a+postexploitation+tool/25912/&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt;. In this one, we take a look at a vulnerability in the way Windows handles desktop.ini files, which makes it possible to use them as an interesting post-exploitation tool.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;UPDATE 27. 5. 2020: I put together a shor video demonstrating the vulnerabiltiy while preparing materials for &lt;a href=&#34;https://www.sans.org/event/sansfire-2020/&#34;&gt;SANSFIRE 2020&lt;/a&gt;. You may find it &lt;a href=&#34;https://www.youtube.com/watch?v=pVqJiaUnstA&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Vulnerability</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Post-exploitation</category>
            
          
            
              <category>Red teaming</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2020</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>SANS ISC Diary - Discovering contents of folders in Windows without permissions</title>
        <link>https://untrustednetwork.net/en/2020/02/18/sans-isc-diary-discovering-contents-of-folders-in-windows-without-permissions/</link>
        <pubDate>Tue, 18 Feb 2020 07:18:21 +0100</pubDate>
        
        <atom:modified>Tue, 18 Feb 2020 07:18:21 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2020/02/18/sans-isc-diary-discovering-contents-of-folders-in-windows-without-permissions/</guid>
        <description>A Diary of mine was published today on the SANS Internet Storm Center. This one deals with a strange side effect of the way in which Windows deals with file permissions, which enables any user, regardless of permissions, to brute-force contents of any local folder.
UPDATE 20. 5. 2020: I put together a shor video demonstrating the weakness/vulnerability while preparing materials for SANSFIRE 2020. You may find it here.</description>
        <content:encoded>&lt;p&gt;A &lt;a href=&#34;https://isc.sans.edu/forums/diary/Discovering+contents+of+folders+in+Windows+without+permissions/25816/&#34;&gt;Diary&lt;/a&gt; of mine was published today on the &lt;a href=&#34;https://isc.sans.edu/&#34;&gt;SANS Internet Storm Center&lt;/a&gt;. This one deals with a strange side effect of the way in which Windows deals with file permissions, which enables any user, regardless of permissions, to brute-force contents of any local folder.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;UPDATE 20. 5. 2020: I put together a shor video demonstrating the weakness/vulnerability while preparing materials for &lt;a href=&#34;https://www.sans.org/event/sansfire-2020/&#34;&gt;SANSFIRE 2020&lt;/a&gt;. You may find it &lt;a href=&#34;https://www.youtube.com/watch?v=5yT-QFdKOqg&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;img src=&#34;https://untrustednetwork.net/images/isc/isc-diary.jpg&#34; alt=&#34;ISC diary&#34;&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        <media:content url="https://untrustednetwork.netimages/isc.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>SANS</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Vulnerability</category>
            
          
        
        
          
            
              <category>News</category>
            
          
            
              <category>2020</category>
            
          
        
        
          
            
              <category>SANS ISC Diary</category>
            
          
        
      </item>
      
      <item>
        <title>Looking back at September 2015</title>
        <link>https://untrustednetwork.net/en/2015/10/18/looking-back-at-september-2015/</link>
        <pubDate>Sun, 18 Oct 2015 16:13:47 +0100</pubDate>
        
        <atom:modified>Sun, 18 Oct 2015 16:13:47 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2015/10/18/looking-back-at-september-2015/</guid>
        <description>Information concerning number of devices vulnerable to Heartbleed vulnerability has appeared in the news during September. Given that the existence of Heartbleed was made public almost a year and a half ago it may be surprising that the number of vulnerable devices exceeds 200.000.
Affair concerning the Stagefright vulnerability (which was mentioned in the last Looking back) continued in September when Zimperium – the company which discovered Stagefright – released a proof-of-concept code which exploits the vulnerability.</description>
        <content:encoded>&lt;p&gt;Information concerning number of devices &lt;a href=&#34;http://www.theinquirer.net/inquirer/news/2426409/heartbleed-still-affects-200-000-devices-because-vendors-are-lazy-maybe&#34;&gt;vulnerable to Heartbleed&lt;/a&gt; vulnerability has appeared in the news during September. Given that the existence of Heartbleed was made public almost a year and a half ago it may be surprising that the number of vulnerable devices exceeds 200.000.&lt;br /&gt;
Affair concerning the Stagefright vulnerability (which was mentioned in the &lt;a href=&#34;https://www.untrustednetwork.net/en/2015/09/08/looking-back-at-august-2015/&#34;&gt;last Looking back&lt;/a&gt;) continued in September when Zimperium – the company which discovered Stagefright – &lt;a href=&#34;http://arstechnica.com/security/2015/09/attack-code-exploiting-androids-critical-stagefright-bugs-is-now-public/&#34;&gt;released&lt;/a&gt; a proof-of-concept code which exploits the vulnerability.&lt;br /&gt;
A stealth malware hidden in modified Cisco IOS images and named &lt;a href=&#34;http://arstechnica.com/security/2015/09/malicious-cisco-router-backdoor-found-on-79-more-devices-25-in-the-us/&#34;&gt;SYNful knock&lt;/a&gt; has been discovered on tens of Cisco routers around the world. The malware functions as a backdoor and besides the (persistent) IOS-embedded main component uses tens of modules which provide further functionality which it loads into volatile memory.&lt;br /&gt;
It should be mentioned that Google, Microsoft and Mozzila made a &lt;a href=&#34;http://threatpost.com/google-mozilla-microsoft-to-sever-rc4-support-in-early-2016/114498/&#34;&gt;press release&lt;/a&gt; announcing that their browsers will stop supporting the RC4 encryption algorithm early next year.&lt;br /&gt;
One final piece of interesting news we will mention has been the discovery of a malware targeted at online poker players. The trojan horse is named &lt;a href=&#34;http://www.welivesecurity.com/2015/09/17/the-trojan-games-odlanor-malware-cheats-at-poker/&#34;&gt;Odlanor&lt;/a&gt; and captures screenshots of applications used for playing poker online and then sends them to the attacker.&lt;/p&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        
        
        
        
          
            
              <category>Heartbleed</category>
            
          
            
              <category>Vulnerability</category>
            
          
            
              <category>Cisco</category>
            
          
            
              <category>Malware</category>
            
          
            
              <category>Google</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Mozzila</category>
            
          
        
        
          
            
              <category>2015</category>
            
          
        
        
          
            
              <category>Looking back</category>
            
          
        
      </item>
      
      <item>
        <title>Looking back at April 2015</title>
        <link>https://untrustednetwork.net/en/2015/05/09/looking-back-at-april-2015/</link>
        <pubDate>Sat, 09 May 2015 20:51:28 +0100</pubDate>
        
        <atom:modified>Sat, 09 May 2015 20:51:28 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2015/05/09/looking-back-at-april-2015/</guid>
        <description>During April, we have witnessed - among others - a discovery of an 18 years old &amp;ldquo;Redirect to SMB&amp;rdquo; vulnerability which can be used to attack all versions of Windows released since then. The vulnerability can be exploited in cases when attacker has some control over the network, enabling him to gain user login information by redirecting of network traffic to a malicious SMB (server message block) server. The server forces the target to automatic authorization process during which the target sends users login, domain and hashed password.</description>
        <content:encoded>&lt;p&gt;During April, we have witnessed - among others - a discovery of an 18 years old &lt;a href=&#34;https://autoblog.postblue.info/autoblogs/lamaredugoffrblog_a1de86d064e376dc283723997fd86bde6ba2d492/media/44593e6c.RedirectToSMB_public_whitepaper.pdf&#34;&gt;&amp;ldquo;Redirect to SMB&amp;rdquo;&lt;/a&gt; vulnerability which can be used to attack all versions of Windows released since then. The vulnerability can be exploited in cases when attacker has some control over the network, enabling him to gain user login information by redirecting of network traffic to a malicious SMB (server message block) server. The server forces the target to automatic authorization process during which the target sends users login, domain and hashed password.&lt;br /&gt;
Next to this vulnerability an April &lt;a href=&#34;https://blog.trendmicro.com/trendlabs-security-intelligence/enterprises-hit-by-bartalex-macro-malware-in-recent-spam-outbreak/&#34;&gt;discovery of a modern macro malware BALTEX&lt;/a&gt;. It spreads using phishing messages with a link to a page containing an infected Word document and instructions to enable macros. After the downloaded document is opened, the macro downloads a variant of DYRE banking malware.&lt;br /&gt;
It is also worth mentioning that the &lt;a href=&#34;http://www.rsaconference.com/&#34;&gt;RSA conference&lt;/a&gt; was held at the end of April.&lt;/p&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        
        
        
        
          
            
              <category>Microsoft</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Malware</category>
            
          
            
              <category>RSA</category>
            
          
        
        
          
            
              <category>2015</category>
            
          
        
        
          
            
              <category>Looking back</category>
            
          
        
      </item>
      
      <item>
        <title>Looking back at March 2015</title>
        <link>https://untrustednetwork.net/en/2015/04/01/looking-back-at-march-2015/</link>
        <pubDate>Wed, 01 Apr 2015 00:00:24 +0100</pubDate>
        
        <atom:modified>Wed, 01 Apr 2015 00:00:24 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2015/04/01/looking-back-at-march-2015/</guid>
        <description>Looking back at March, probably the most important information security news has been discovery of a significant vulnerability (which could be exploited using a FREAK attack) in some TLS/SSL implementations, including the ones used by Windows operating systems.
Another worth while news has been a discovery of a new campaign aimed at energy sector companies in the Middle East. Trojan Laizok - a reconnaissance malware for gathering information about infected systems - has been used in the campaign, along with other malicious programs which have been modified for specific systems based on the information gathered by Laizok.</description>
        <content:encoded>&lt;p&gt;Looking back at March, probably the most important information security news has been &lt;a href=&#34;https://www.untrustednetwork.net/en/2015/03/04/freak-a-high-impact-vulnerability-in-tls-ssl/&#34;&gt;discovery&lt;/a&gt; of a significant vulnerability (which could be exploited using a FREAK attack) in some TLS/SSL implementations, including the ones used by Windows operating systems.&lt;br /&gt;
Another worth while news has been a discovery of a new campaign aimed at energy sector companies in the Middle East. Trojan Laizok - a reconnaissance malware for gathering information about infected systems - has been used in the campaign, along with other malicious programs which have been modified for specific systems based on the information gathered by Laizok.&lt;br /&gt;
A mention should also be made about two very powerful DDoS attacks made during the second half of the month - first one was targeted at Greatfire.org and the second one at GitHub. According to &lt;a href=&#34;http://www.tripwire.com/state-of-security/latest-security-news/github-hit-with-massive-ddos-attack-china-allegedly-involved/&#34;&gt;published analysis&lt;/a&gt; China was the source of both attacks.&lt;br /&gt;
Finally, at the end of &amp;ldquo;Looking back&amp;rdquo; we shoud mention that in course of March the &lt;a href=&#34;https://www.untrustednetwork.net/en/2015/03/10/rowhammer-an-attack-which-uses-a-weakness-in-ddr3-memory/&#34;&gt;Rowhammer&lt;/a&gt; attack was made public. It is based on changing specific bits in memory by exploiting a weakness in DDR3 memories which leads to priviledge escalation.&lt;/p&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        
        
        
        
          
            
              <category>Microsoft</category>
            
          
            
              <category>Rowhammer</category>
            
          
            
              <category>Windows</category>
            
          
            
              <category>Malware</category>
            
          
        
        
          
            
              <category>2015</category>
            
          
        
        
          
            
              <category>Looking back</category>
            
          
        
      </item>
      
      <item>
        <title>Looking back at February 2015</title>
        <link>https://untrustednetwork.net/en/2015/03/03/looking-back-at-february-2015/</link>
        <pubDate>Tue, 03 Mar 2015 09:58:57 +0100</pubDate>
        
        <atom:modified>Tue, 03 Mar 2015 09:58:57 +0100</atom:modified>
        <guid>https://untrustednetwork.net/en/2015/03/03/looking-back-at-february-2015/</guid>
        <description>Dramatic information security incidents and news were unfortunately fairly common in February – we will shortly remember three of the most interesting ones.
Most attention was probably gained by a story about an alleged theft of massive amount of encryption keys used in mobile communication from the network of Dutch company Gemalto (a major SIM card supplier) by NSA and GCHQ. The keys could be used to decrypt live communication and also, for example, remotely inject malicious code into end devices.</description>
        <content:encoded>&lt;p&gt;Dramatic information security incidents and news were unfortunately fairly common in February – we will shortly remember three of the most interesting ones.&lt;/p&gt;
&lt;p&gt;Most attention was probably gained by a story about an alleged theft of massive amount of encryption keys used in mobile communication from the network of Dutch company Gemalto (a major SIM card supplier) by NSA and GCHQ. The keys could be used to decrypt live communication and also, for example, remotely inject malicious code into end devices. Source of the story has been The Intercept, citing a &lt;a href=&#34;https://firstlook.org/theintercept/document/2015/02/19/cne-access-core-mobile-networks-2/&#34;&gt;document&lt;/a&gt; from 2010 which was acquired by Edward Snowden, formerly from the NSA. After the news went public Gemalto stock took a &lt;a href=&#34;http://www.theregister.co.uk/2015/02/20/gemalto_sim_surveillance_fallout/&#34;&gt;serious hit&lt;/a&gt;. The company responded couple of days later by a &lt;a href=&#34;http://www.gemalto.com/press/Pages/Gemalto-presents-the-findings-of-its-investigations-into-the-alleged-hacking-of-SIM-card-encryption-keys.aspx&#34;&gt;press release&lt;/a&gt; admitting that operation by NSA and GCHQ resulting in penetration of internal company network probably happened, but emphasizing that the penetration “could not have led to a massive theft of encryption keys”. Gemalto further stated that “in the case of eventual key theft, the intelligence services would only be able to spy on second generation 2G mobile network” since “3G and 4G networks are not vulnerable to this type of attack”.&lt;/p&gt;
&lt;p&gt;Another high impact February news has been that the Superfish adware (which is used to inject ads into viewed web pages based on analysis of viewed pictures) which Lenovo used to &lt;a href=&#34;http://www.theregister.co.uk/2015/02/19/superfish_lenovo_spyware/&#34;&gt;preinstall&lt;/a&gt; on their laptops installed a self-signed root certificate. Using that, the adware could generate certificates for web pages which user viewed using encrypted connections, replacing the legitimate certificates and compromising security of communication between the user and the web page. Superfish was then able to analyze and alter the SSL encrypted communication. Furthermore, since the root certificated seems to have been always the same and itself &lt;a href=&#34;http://www.tripwire.com/state-of-security/security-data-protection/superfish-lenovo-adware-faq/&#34;&gt;not very secure&lt;/a&gt;, its presence in a system constitutes a vulnerability which can be used quite easily by a potential attacker. Since discovering this, &lt;a href=&#34;http://www.cnet.com/news/lenovo-hit-by-lawsuit-over-superfish-adware/&#34;&gt;lawsuits&lt;/a&gt; have been filed against Lenovo and web pages of the company have been &lt;a href=&#34;http://www.v3.co.uk/v3-uk/news/2397144/lizard-squad-hackers-attack-lenovo-after-superfish-scandal&#34;&gt;defaced&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It should also be noted that in the course of February, after being criticized by Microsoft (among others), Google decided to &lt;a href=&#34;http://www.infosecurity-magazine.com/news/google-blinks-first-with-project/&#34;&gt;change&lt;/a&gt; the policy of its Project Zero – an initiative which, after a vulnerability has been discovered in an application, gave 90-day deadline to its developers to work on a patch. After the deadline has passed the vulnerability was made public regardless of existence of a patch or its planed later release. This has been the case for Microsoft and a vulnerability in Windows 8.1 when the 90-day deadline ended &lt;a href=&#34;http://blogs.technet.com/b/msrc/archive/2015/01/11/a-call-for-better-coordinated-vulnerability-disclosure.aspx&#34;&gt;two days&lt;/a&gt; before planned release of a patch during Patch Tuesday, regular release of updates and patches by Microsoft. Google now grants developers up to 2 weeks reprieve after the deadline has passed, provided they are actively working on patching the vulnerability.&lt;/p&gt;
</content:encoded>
        <dc:creator>Jan Kopriva</dc:creator>
        
        
        
        
          
            
              <category>Gemalto</category>
            
          
            
              <category>NSA</category>
            
          
            
              <category>GCHQ</category>
            
          
            
              <category>Snowden</category>
            
          
            
              <category>Lenovo</category>
            
          
            
              <category>Adware</category>
            
          
            
              <category>Google</category>
            
          
            
              <category>Microsoft</category>
            
          
            
              <category>Project Zero</category>
            
          
        
        
          
            
              <category>2015</category>
            
          
        
        
          
            
              <category>Looking back</category>
            
          
        
      </item>
      

    
  </channel>
</rss>