<?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>Sahi Pro (&lt;=8.x) Directory traversal Archives -</title>
	<atom:link href="https://barriersec.com/category/disclosures/sahi-pro-8-x-directory-traversal/feed/" rel="self" type="application/rss+xml" />
	<link>https://barriersec.com/category/disclosures/sahi-pro-8-x-directory-traversal/</link>
	<description></description>
	<lastBuildDate>Mon, 14 Sep 2020 03:01:05 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.2.15</generator>

<image>
	<url>https://barriersec.com/wp-content/uploads/cropped-Monochrome-on-Transparent-32x32.png</url>
	<title>Sahi Pro (&lt;=8.x) Directory traversal Archives -</title>
	<link>https://barriersec.com/category/disclosures/sahi-pro-8-x-directory-traversal/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>CVE-2018-20470 &#8211; Sahi pro ( </title>
		<link>https://barriersec.com/2019/06/cve-2018-20470-sahi-pro/</link>
		
		<dc:creator><![CDATA[goutham madhwaraj]]></dc:creator>
		<pubDate>Tue, 11 Jun 2019 15:48:35 +0000</pubDate>
				<category><![CDATA[disclosures]]></category>
		<category><![CDATA[Sahi Pro (<=8.x) Directory traversal]]></category>
		<category><![CDATA[7.x]]></category>
		<category><![CDATA[8.x]]></category>
		<category><![CDATA[automation tool]]></category>
		<category><![CDATA[disclosure]]></category>
		<category><![CDATA[sahi pro]]></category>
		<guid isPermaLink="false">https://barriersec.com/?p=516</guid>

					<description><![CDATA[<p>Sahi pro is a application automation tool which is quite popular among automation testers . (https://sahipro.com/ )   Being a former&#8230;</p>
<p>The post <a rel="nofollow" href="https://barriersec.com/2019/06/cve-2018-20470-sahi-pro/">CVE-2018-20470 &#8211; Sahi pro ( &lt;= 8.x ) Directory traversal</a> appeared first on <a rel="nofollow" href="https://barriersec.com"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Sahi pro is a application automation tool which is quite popular among automation testers . (<a href="https://sahipro.com/">https://sahipro.com/ </a>)   Being a former automation tester who transitioned to penetration testing,  who also heavily relied on sahi pro for day to day automation activities, An idea raced in my mind to combine both and start hunting for some security bugs in their products. And here is one of the issue that i found in their product.</p>
<p>sahi pro has some interesting features such  as <strong>web reporting interface</strong> and <strong>web editor</strong> which combined and forms report module which aggregates all the automated test execution / suite .  It was found that we can view the source code of any sahi file in the editor to check debug logs, where it highlights failed line or execution flow etc</p>
<p>report interface url can be found at the following location :</p>
<p><strong><a href="http://localhost:9999/logs" target="_blank" rel="noopener noreferrer">http://&lt;ip&gt;:&lt;port&gt;/logs</a> </strong></p>
<p>In the web editor module , it was observed that there  exists a directory traversal vulnerability which allows any user on the same network to view any files on the victim machine running sahi pro automation software. sahi pro allows users to restrict file access for scripts in their configuration file, but this particular module seems to be vulnerable due to lack of server side validations.</p>
<p><strong>Proof of concept  :</strong></p>
<p><img decoding="async" loading="lazy" class="aligncenter wp-image-523" src="https://barriersec.com/wp-content/uploads/original.png" alt="" width="677" height="258" srcset="https://barriersec.com/wp-content/uploads/original.png 1920w, https://barriersec.com/wp-content/uploads/original-300x114.png 300w, https://barriersec.com/wp-content/uploads/original-768x292.png 768w, https://barriersec.com/wp-content/uploads/original-1024x389.png 1024w" sizes="(max-width: 677px) 100vw, 677px" /></p>
<p>Fig 1 :  shows the reports module which displays and highlights the source code of sahi script file for debugging .</p>
<p>here the get parameter <strong>href </strong>is vulnerable to directory traversal(can also include remote files  to cause Denial of service on victim browser)</p>
<p>Here href get parameter is referring to location :</p>
<p><strong>href=scripts/csv_injection_demo.sah</strong></p>
<p>if its modified to <strong>href=../../supersecret/password.txt </strong>, contents of crucial internal files of the victim machine.</p>
<p><img decoding="async" loading="lazy" class="size-full wp-image-527 aligncenter" src="https://barriersec.com/wp-content/uploads/proof1.png" alt="" width="1412" height="483" srcset="https://barriersec.com/wp-content/uploads/proof1.png 1412w, https://barriersec.com/wp-content/uploads/proof1-300x103.png 300w, https://barriersec.com/wp-content/uploads/proof1-768x263.png 768w, https://barriersec.com/wp-content/uploads/proof1-1024x350.png 1024w" sizes="(max-width: 1412px) 100vw, 1412px" /></p>
<p>Fig 2 : vulnerable to directory traversal.</p>
<p>another snapshot which disclose contents of <strong>win.ini</strong> file</p>
<p><img decoding="async" loading="lazy" class="size-full wp-image-528 aligncenter" src="https://barriersec.com/wp-content/uploads/proof2.png" alt="" width="1353" height="631" srcset="https://barriersec.com/wp-content/uploads/proof2.png 1353w, https://barriersec.com/wp-content/uploads/proof2-300x140.png 300w, https://barriersec.com/wp-content/uploads/proof2-768x358.png 768w, https://barriersec.com/wp-content/uploads/proof2-1024x478.png 1024w" sizes="(max-width: 1353px) 100vw, 1353px" /></p>
<p>Fig 3 : vulnerable to directory traversal.</p>
<p><strong>URL vulnerable :</strong></p>
<p><strong>http://&lt;ip&gt;:&lt;port&gt;/_s_/dyn/Log_highlight?href=../../../../windows/win.ini&amp;n=1#selected</strong></p>
<p><strong>Disclosure timeline :</strong></p>
<p>Notified on : <strong>8 / December / 2018</strong></p>
<p>suggested quick fix till the official patch is released : password protect web reports module</p>
<p>Affected versions : all versions of <strong>sahi pro ( &lt;= 8.x ) (web application automation )</strong></p>
<p><strong>vendor website</strong> :  https://sahipro.com/</p>
<p>The post <a rel="nofollow" href="https://barriersec.com/2019/06/cve-2018-20470-sahi-pro/">CVE-2018-20470 &#8211; Sahi pro ( &lt;= 8.x ) Directory traversal</a> appeared first on <a rel="nofollow" href="https://barriersec.com"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
