<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tim Kent on Medium]]></title>
        <description><![CDATA[Stories by Tim Kent on Medium]]></description>
        <link>https://medium.com/@tim.kent?source=rss-2c7717e71ba2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*avzwzyv63qVWE2hW</url>
            <title>Stories by Tim Kent on Medium</title>
            <link>https://medium.com/@tim.kent?source=rss-2c7717e71ba2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:43:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tim.kent/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[XSS in Dynamics 365]]></title>
            <link>https://medium.com/tsscyber/xss-in-dynamics-365-25c800aac473?source=rss-2c7717e71ba2------2</link>
            <guid isPermaLink="false">https://medium.com/p/25c800aac473</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Tim Kent]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 03:59:03 GMT</pubDate>
            <atom:updated>2018-11-12T06:36:39.597Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently tested an application hosted within Microsoft’s Dynamics 365 online services platform. During the test I discovered a <a href="https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)">Cross-Site Scripting (XSS) vulnerability</a>.</p><p>Dynamics 365 is typically extended with customer code which can be a source of trouble, however the vulnerability discovered was in the Dynamics 365 product itself.</p><p>After obtaining permission from the client, I worked with the Microsoft Security Response Center to fix the issue. Now that it has been patched (as of the 18th October 2018) I can disclose the details of this vulnerability:</p><blockquote>Within Dynamics 365, the “Personal Document Template: Information” page reflects the user’s name without encoding it properly, so if the field is injected with a JavaScript payload, it will be run unchecked.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*S--p7rCwi7gXYJbRJGvg8g.png" /></figure><p>In the Dynamics 365 tenant being tested, I was able to change the First Name and Last Name values for the “Application User” (this appears to be separate to the Azure AD User, which was locked down).</p><p>I set the First Name field to contain a JavaScript payload. No special tricks needed; the payload was simply “&lt;/script&gt;&lt;script&gt;alert(‘xss’)&lt;/script&gt;”.</p><p>The First Name and Last Name fields are used throughout the application and are usually encoded safely. However the “Personal Document Template: Information” page reflects these fields without encoding and runs the payload.</p><p>With this payload set, a malicious user can create or update any template they have access to, and direct a victim to the template information page. When the owner and last modified fields are loaded into the victim’s browser, the payload is fired.</p><p>As you can see, this was not a complicated attack in hindsight but it has the potential to have a large impact. It is also a good example of how assumptions should not be made about the code base being tested. If I had assumed the product code had been extensively tested and was secure, then this simple XSS injection would have been overlooked.</p><p>The takeaway is to try and remember to sanitise and encode all inputs/outputs, regardless of what they are used for, and not to make assumptions but rely on empirical evidence as a penetration tester!</p><p>Thanks to Microsoft for acting as a responsible vendor in accepting and patching this vulnerability in such a short period of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25c800aac473" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tsscyber/xss-in-dynamics-365-25c800aac473">XSS in Dynamics 365</a> was originally published in <a href="https://medium.com/tsscyber">TSS - Trusted Security Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>