<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thandermax</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thandermax"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Thandermax"/>
		<updated>2026-05-25T05:13:13Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Code_Injection&amp;diff=7913</id>
		<title>Code Injection</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Code_Injection&amp;diff=7913"/>
				<updated>2006-07-24T08:41:45Z</updated>
		
		<summary type="html">&lt;p&gt;Thandermax: /* Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:Attack}}&lt;br /&gt;
&lt;br /&gt;
{{Template:Stub}}&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
This article should cover attacks based on injecting code into a running application.&lt;br /&gt;
&lt;br /&gt;
==Examples ==&lt;br /&gt;
&lt;br /&gt;
If server side scripting is enabled in some address (such as guestbook , where user can insert data)&lt;br /&gt;
then the SSI attack can be done.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Such as :&lt;br /&gt;
&lt;br /&gt;
&amp;lt; !--#exec cmd=&amp;quot;ls&amp;quot; -- &amp;gt;&lt;br /&gt;
&lt;br /&gt;
will show all the files in current directory is the server is on a UNIX/LINUX machine.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
for Windows platform :          &amp;lt; !--#exec cmd=&amp;quot;dir&amp;quot;-- &amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for destructive purpose also , as the commands are executed in root/admin previlage.&lt;br /&gt;
&lt;br /&gt;
Such as   &amp;lt; !--#exec cmd=&amp;quot;format c:&amp;quot;-- &amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Related Threats==&lt;br /&gt;
&lt;br /&gt;
==Related Attacks==&lt;br /&gt;
&lt;br /&gt;
==Related Vulnerabilities==&lt;br /&gt;
&lt;br /&gt;
==Related Countermeasures==&lt;br /&gt;
&lt;br /&gt;
[[Category:Attack]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Injection Attack]]&lt;/div&gt;</summary>
		<author><name>Thandermax</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Code_Injection&amp;diff=7912</id>
		<title>Code Injection</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Code_Injection&amp;diff=7912"/>
				<updated>2006-07-24T08:40:12Z</updated>
		
		<summary type="html">&lt;p&gt;Thandermax: /* Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:Attack}}&lt;br /&gt;
&lt;br /&gt;
{{Template:Stub}}&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
This article should cover attacks based on injecting code into a running application.&lt;br /&gt;
&lt;br /&gt;
==Examples ==&lt;br /&gt;
&lt;br /&gt;
If server side scripting is enabled in some address (such as guestbook , where user can insert data)&lt;br /&gt;
then the SSI attack can be done.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Such as :&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--#exec cmd=&amp;quot;ls&amp;quot;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
will show all the files in current directory is the server is on a UNIX/LINUX machine.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
for Windows platform :           &amp;lt;!--#exec cmd=&amp;quot;dir&amp;quot;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This can be used for destructive purpose also , as the commands are executed in root/admin previlage.&lt;br /&gt;
&lt;br /&gt;
Such as   &amp;lt;!--#exec cmd=&amp;quot;format c:&amp;quot;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Related Threats==&lt;br /&gt;
&lt;br /&gt;
==Related Attacks==&lt;br /&gt;
&lt;br /&gt;
==Related Vulnerabilities==&lt;br /&gt;
&lt;br /&gt;
==Related Countermeasures==&lt;br /&gt;
&lt;br /&gt;
[[Category:Attack]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Injection Attack]]&lt;/div&gt;</summary>
		<author><name>Thandermax</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Detect_intrusions&amp;diff=7911</id>
		<title>Detect intrusions</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Detect_intrusions&amp;diff=7911"/>
				<updated>2006-07-24T08:30:43Z</updated>
		
		<summary type="html">&lt;p&gt;Thandermax: /* Categories */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Template:Principle}}&lt;br /&gt;
&lt;br /&gt;
{{Template:Stub}}&lt;br /&gt;
&lt;br /&gt;
==Categories==&lt;br /&gt;
&lt;br /&gt;
[[Category:Principle]]&lt;br /&gt;
&lt;br /&gt;
'''Log All user access (IP,Username,Time ,web request etc..).'''&lt;br /&gt;
&lt;br /&gt;
If you do this ,then someday when your application /site is down/hacked you can trace the culprit and check what went wrong.&lt;br /&gt;
&lt;br /&gt;
You may ask , if the user uses an proxy , Though it will help. As &amp;quot;what happened&amp;quot; is logged and the exploit can be fixed more easily.&lt;/div&gt;</summary>
		<author><name>Thandermax</name></author>	</entry>

	</feed>