Security Considerations when Working with XML Data
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
This topic discusses security issues that you need to know about when working with the XML Editor or the XSLT debugger.
XML Editor
The XML Editor is based on the Visual Studio Text Editor. It relies on the System.Xml and System.Xml.Xsl classes to handle many of the XML processes.
XSLT transformations are executed in a new application domain. The XSLT transformations are sandboxed; that is, the code access security policy of your computer is used to determine the restricted permissions based on where the XSLT style sheet is located. For example, style sheets from an Internet location have the most restricted permissions, whereas style sheets copied to your hard drive run with Full Trust.
The XslCompiledTransform class is used to compile the XSLT to Microsoft intermediate language for faster performance during execution.
Schemas that point to an external location in the catalog file are automatically downloaded when the XML Editor first loads. The XmlSchemaSet class is used to compile the schemas. The catalog file that ships with the XML Editor does not have links to any external schemas. The user has to explicitly add a reference to the external schema before the XML Editor downloads the schema file. HTTP downloading can be disabled via the Miscellaneous Tools Options page for the XML Editor.
The XML Editor uses the System.Net classes to download schemas
XSLT Debugger
The XSLT debugger utilizes the Visual Studio managed debug engine and classes from the System.Xml and System.Xml.Xsl namespace.
The XSLT debugger runs each XSLT transformation in a sandboxed application domain. The code access security policy of your computer is used to determine the restricted permissions based on where the XSLT style sheet is located. For example, style sheets from an Internet location have the most restricted permissions, whereas style sheets copied to your hard drive run with Full Trust.
The XSLT style sheet is compiled using the XslCompiledTransform class.
The XSLT expression evaluator is loaded by the managed debug engine. The managed debug engine assumes that all code is run from the user's local computer. Accordingly, the XslCompiledTransform class downloads the XSLT file to the user's local computer. The possibility that an elevation in execution privilege could occur is mitigated by executing all XSLT transformations in a new application domain with restricted permissions