<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=ClickOnce_Security</id>
		<title>ClickOnce Security - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=ClickOnce_Security"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=ClickOnce_Security&amp;action=history"/>
		<updated>2026-05-11T08:40:01Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=ClickOnce_Security&amp;diff=116308&amp;oldid=prev</id>
		<title>Deepnov: Vulnerabilities in Microsoft's ClickOnce technology for client server applications written in .net</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=ClickOnce_Security&amp;diff=116308&amp;oldid=prev"/>
				<updated>2011-08-26T10:22:14Z</updated>
		
		<summary type="html">&lt;p&gt;Vulnerabilities in Microsoft&amp;#039;s ClickOnce technology for client server applications written in .net&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;p&amp;gt;Microsoft's ClickOnce technology, which is quite similar to Java WebStart has a number of vulnerabilities&amp;amp;nbsp;and&amp;amp;nbsp;any ClickOnce client server application developed on dotnet technology&amp;amp;nbsp;can be completely compromised if appropriate security controls are not used.&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;1. The&amp;amp;nbsp;ILDASM tool available within the .net framework&amp;amp;nbsp;can be used to disassemble the application client and any database related logic/info can be exposed to hackers.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;2. The Disassembled code can even leak encryption keys initialized inside the client code.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;3. The code can be reassembled back to DLLs and EXEs using the ILASM tool from the command line.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;4. Code signed by Authenticode can also be bypassed by intercepting the response data and removing the signature. (Please&amp;amp;nbsp;visit the link below)&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;5. By cracking the client application, every possible security control implemented on the client can be broken. For eg: Authorization, Input Validation &amp;amp;amp; Cryptographic storage.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Possible Mitigation controls include:&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;1. Complete code obfuscation on the client side application to prevent easy tampering of Intermediate Language code.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;2. Sign all the client&amp;amp;nbsp;assemblies with a strong name. (Assembly loader can detect tampered assembly)&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;3. Use Authenticode to sign the application.&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;Please see the below link for Man-In-The-Middle vulnerabilities:&lt;br /&gt;
&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;http://www.securityfocus.com/archive/1/512450&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;/div&gt;</summary>
		<author><name>Deepnov</name></author>	</entry>

	</feed>