# XML Background ## eXtensible Markup Language ### What is XML? XML (eXtensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. It is a markup language used for storing and transporting data. ### Why we use XML? 1\. XML is platform-independent and programming language independent, thus it can be used on any system and supports the technology change when that happens.\ \ 2\. The data stored and transported using XML can be changed at any point in time without affecting the data presentation.\ \ 3\. XML allows validation using DTD and Schema. This validation ensures that the XML document is free from any syntax error.\ \ 4\. XML simplifies data sharing between various systems because of its platform-independent nature. XML data doesn’t require any conversion when transferred between different systems. ### Syntax Every XML document mostly starts with what is known as XML Prolog.\ \ `` Above the line is called XML prolog and it specifies the XML version and the encoding used in the XML document. This line is not compulsory to use but it is considered a \`good practice\` to put that line in all your XML documents.\ \ Every XML document must contain a \`ROOT\` element. For example: ``\ ``\ `falcon`\ `feast`\ `About XXE`\ `Teach about XXE`\ ``
In the above example the `` is the ROOT element of that document and ``, ``, ``, `` are the children elements. If the XML document doesn't have any root element then it would be considered`wrong` or `invalid` XML doc.\ \ Another thing to remember is that XML is a case sensitive language. If a tag starts like `` then it has to end by `` and not by something like ``(notice the capitalization of `T`)\ \ Like HTML we can use attributes in XML too. The syntax for having attributes is also very similar to HTML. For example:\ `You need to learn about XXE` In the above example `category` is the attribute name and `message` is the attribute value. ## Document Type Definition (DTD) Before we move on to start learning about XXE we'll have to understand what is DTD in XML. DTD stands for Document Type Definition. A DTD defines the structure and the legal elements and attributes of an XML document. Let us try to understand this with the help of an example. Say we have a file named `note.dtd` with the following content:
` ]>`\ Now we can use this DTD to validate the information of some XML document and make sure that the XML file conforms to the rules of that DTD. Ex: Below is given an XML document that uses `note.dtd`\\ \\ \\ \falcon\\ \feast\\ \hacking\\ \XXE attack\\ \ So now let's understand how that DTD validates the XML. Here's what all those terms used in `note.dtd` mean
* !DOCTYPE note - Defines a root element of the document named note * !ELEMENT note - Defines that the note element must contain the elements: "to, from, heading, body" * !ELEMENT to - Defines the `to` element to be of type "#PCDATA" * !ELEMENT from - Defines the `from` element to be of type "#PCDATA" * !ELEMENT heading - Defines the `heading` element to be of type "#PCDATA" * !ELEMENT body - Defines the body `element` to be of type "#PCDATA" NOTE: #PCDATA means parseable character data. * How do you define a new ELEMENT? * !ELEMENT * How do you define a ROOT element? * !DOCTYPE * How do you define a new ENTITY? * !ENTITY --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wiki.zacheller.dev/web-app-pentest/xml-external-entity/xml-background.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.