1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 |
Title: ====== Microsoft SharePoint 2013 (Cloud) - Persistent Exception Handling Web Vulnerability Date: ===== 2013-09-11 References: =========== http://www.vulnerability-lab.com/get_content.php?id=812 Security Bulletin: MS13-067 http://technet.microsoft.com/de-de/security/bulletin/MS13-067 Microsoft Security Response Center (MSRC) ID: 14096 VL-ID: ===== 812 Common Vulnerability Scoring System: ==================================== 5.7 Introduction: ============= Microsoft SharePoint is a Web application platform developed by Microsoft. First launched in 2001, SharePoint has historically been associated with intranet content management and document management, but recent versions have significantly broader capabilities. Microsoft has two versions of SharePoint available at no cost, but it sells premium editions with additional functionality, and provides a cloud service edition as part of their Office 365 platform (previously BPOS). The product is also sold through a cloud model by many third-party vendors. SharePoint comprises a multipurpose set of Web technologies backed by a common technical infrastructure. By default, SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite. The web tools are designed to be usable by non- technical users. SharePoint can be used to provide intranet portals, document & file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence. It also has system integration, process integration, and workflow automation capabilities. Enterprise application software (e.g. ERP or CRM packages) often provide some SharePoint integration capability, and SharePoint also incorporates a complete development stack based on web technologies and standards-based APIs. As an application platform, SharePoint provides central management, governance, and security controls for implementation of these requirements. The SharePoint platform integrates directly into IIS - enabling bulk management, scaling, and provisioning of servers, as is often required by large organizations or cloud hosting providers. In 2008, the Gartner Group put SharePoint in the<code>leaders</code> quadrant in three of its Magic Quadrants (for search, portals, and enterprise content management). SharePoint is used by 78% of Fortune 500 companies[citation needed]. Between 2006 to 2011, Microsoft sold over 36.5 million user licenses[citation needed]. (Copy of the Homepage: http://en.wikipedia.org/wiki/Microsoft_SharePoint ) Abstract: ========= The Vulnerability Laboratory Research Team discovered a persistent web vulnerability in the official Microsoft Sharepoint Online (cloud-based) application. Report-Timeline: ================ 2013-02-01: Researcher Notification & Coordination (Benjamin Kunz Mejri) 2013-02-06: Vendor Notification (Microsoft Security Response Center - MSRC) 2013-02-07: Vendor Response/Feedback (Microsoft Security Response Center - MSRC) 2013-09-11: Vendor Fix/Patch (Microsoft Security Bulletin) 2013-09-11: Public Disclosure (Vulnerability Laboratory) Status: ======== Published Affected Products: ================== Microsoft Corp. Product: Sharepoint Online (Cloud-Based) Exploitation-Technique: ======================= Remote Severity: ========= High Details: ======== A persistent input validation vulnerability is detected in the official Microsoft Sharepoint 2013 Online (cloud-based) web-application. The vulnerability allows remote attackers to inject own malicious script code to a vulnerable module on application-side (persistent). The vulnerability is located in the <code>Sharepoint Online Cloud 2013 Service</code> section when processing to request the <code>Berechtigungen für den Metadatenspeicher festlegen</code> module with manipulated ms-descriptionText > ctl00_PlaceHolderDialogBodySection_ PlaceHolderDialogBodyMainSection_ValSummary parameters. The persistent injected script code execution occurs in the main invalid BDC Übereinstimmung</code> web application exception-handling. The vulnerability can be exploited with a low (restricted) privileged application user account and low or medium required user interaction. Successful exploitation of the vulnerability result in persistent session hijacking, persistent phishing, stable external redirect, stable external malware loads and persistent vulnerable module context manipulation. Vulnerable Service(s): [+] Microsoft - Sharepoint Online (cloud-based) Vulnerable Module(s): [+] Berechtigungen für den Metadatenspeicher festlegen - BDC Metadatenspeicher zuweisen Vulnerable Parameter(s): [+] ms-descriptionText > ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_ValSummary [+] TA_ManageBDCPermissions_data Affected Module(s): [+] BDC Übereinstimmung > Exception Handling Proof of Concept: ================= The persistent input validation web vulnerability can be exploited by remote attackers with low required user interaction and low privileged sharepoint cloud application user account. For demonstration or reproduce ... Review: Berechtigungen für den Metadatenspeicher festlegen - Summery > BDC Übereinstimmung > Exception (TA_ManageBDCPermissions_data) <table class="propertysheet" border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> <td class="ms-descriptionText"> <span id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_LabelMessage" class="ms-descriptionText"></span> </td> </tr> <tr> <td class="ms-error"><span id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_LabelErrorMessage"> Fehler beim Versuch, 'IMetadataCatalog' eine Zugriffssteuerungsliste mit dem Namen 'ApplicationRegistry' zuzuweisen. Mindestens ein Benutzer oder eine Gruppe in der Zugriffssteuerungsliste muss über das Recht 'SetPermissions' verfügen, um das Erstellen eines nicht verwaltbaren Objekts zu verhindern.</span></td> </tr> <tr> <td class="ms-descriptionText"> <div id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_ValSummary" style="color:Red;">Mindestens ein Fehler auf der Seite. Beheben Sie Folgendes, bevor Sie fortfahren:<ul><li>Es wurde keine exakte Übereinstimmung für <iframe src="https://www.exploit-db.com/exploits/28238/TA_ManageBDCPermissions_data/vlab.js">%20%20%20 %20"><[PERSISTENT INJECTED SCRIPT CODE!]") <%20%20%20%20"><[PERSISTENT INJECTED SCRIPT CODE!]") < gefunden.</li></ul> </div> </td> </tr> </table> <table border="0" cellspacing="0" cellpadding="0" width="100%" class="ms-authoringcontrols"> <tr> <td> ---------- <table class="propertysheet" border="0" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr> <td class="ms-descriptionText"> <span id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_LabelMessage" class="ms-descriptionText"></span> </td> </tr> <tr> <td class="ms-error"><span id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_LabelErrorMessage"> Fehler beim Versuch, 'IMetadataCatalog' eine Zugriffssteuerungsliste mit dem Namen 'ApplicationRegistry' zuzuweisen. Mindestens ein Benutzer oder eine Gruppe in der Zugriffssteuerungsliste muss über das Recht 'SetPermissions' verfügen, um das Erstellen eines nicht verwaltbaren Objekts zu verhindern.</span></td> </tr> <tr> <td class="ms-descriptionText"> <div id="ctl00_PlaceHolderDialogBodySection_PlaceHolderDialogBodyMainSection_ValSummary" style="color:Red;">Mindestens ein Fehler auf der Seite. Beheben Sie Folgendes, bevor Sie fortfahren:<ul><li>Es wurde keine exakte Übereinstimmung für <iframe src="https://www.exploit-db.com/exploits/28238/TA_ManageBDCPermissions_data/a.txt">%20%20%20%20"><[PERSISTENT INJECTED SCRIPT CODE!]) <<%20[PERSISTENT INJECTED SCRIPT CODE!]) < gefunden.</li></ul> </div> </td> </tr> </table> <table border="0" cellspacing="0" cellpadding="0" width="100%" class="ms-authoringcontrols"> <tr> <td> --- Exception Handling (DE) --- Sie können Administratoren des BDC-Metadatenspeichers zuweisen, indem Sie unten Berechtigungen festlegen. Fehler beim Versuch, 'IMetadataCatalog' eine Zugriffssteuerungsliste mit dem Namen 'ApplicationRegistry' zuzuweisen. Mindestens ein Benutzer oder eine Gruppe in der Zugriffssteuerungsliste muss über das Recht 'SetPermissions' verfügen, um das Erstellen eines nicht verwaltbaren Objekts zu verhindern. Mindestens ein Fehler auf der Seite. Beheben Sie Folgendes, bevor Sie fortfahren: Es wurde keine exakte Übereinstimmung für ... [Injected Context] ... gefunden/festgestellt. Sie können Administratoren des BDC-Metadatenspeichers zuweisen, indem Sie unten Berechtigungen festlegen --- Note: (US) After you’ve added your domain name to Office 365 to use with SharePoint Online and Lync Online, you can create email addresses, Lync Online accounts, and distribution groups that use your custom domain name. You can also use your domain name for a public website hosted on SharePoint Online but there are Use SharePoint Online on a custom domain together with other services. Reference(s): https://benjamin23-admin.sharepoint.com/default.aspx https://benjamin23-admin.sharepoint.com/_layouts/bdc/TA_ViewBDCApplication.aspx Solution: ========= 2013-09-11: Vendor Fix/Patch (Microsoft Security Bulletin) URL: http://technet.microsoft.com/de-de/security/bulletin/MS13-067> Updates Risk: ===== The security risk of the of the persistent input validation vulnerability is estimated as high(-). Credits: ======== Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [www.vulnerability-lab.com] Disclaimer: =========== The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability- Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material. Domains:www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com Contact:admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com Section:www.vulnerability-lab.com/dev - forum.vulnerability-db.com - magazine.vulnerability-db.com Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact (admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission. Copyright © 2013 | Vulnerability Laboratory [Evolution Security] -- VULNERABILITY LABORATORY RESEARCH TEAM DOMAIN: www.vulnerability-lab.com CONTACT: research@vulnerability-lab.com |