[jira] Created: (XERCESC-1854) Serialization does not detect invalid XML characters

Serialization does not detect invalid XML characters
----------------------------------------------------

                 Key: XERCESC-1854
                 URL: https://issues.apache.org/jira/browse/XERCESC-1854
             Project: Xerces-C++
          Issue Type: Bug
          Components: DOM
    Affects Versions: 3.0.1
            Reporter: Boris Kolpackov
             Fix For: 3.1.0
         Attachments: test.cxx

The attached test case serializes an invalid XML 1.0 document that contains a character with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters in an XML 1.0 document.

I've done some digging and it seems that XMLFormatter should check for this. In fast, there is already code for XML 1.1 that checks for these control characters since they need to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0 mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

     [ https://issues.apache.org/jira/browse/XERCESC-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boris Kolpackov updated XERCESC-1854:
-------------------------------------

    Attachment: test.cxx

> Serialization does not detect invalid XML characters
> ----------------------------------------------------
>
>                 Key: XERCESC-1854
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1854
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: DOM
>    Affects Versions: 3.0.1
>            Reporter: Boris Kolpackov
>             Fix For: 3.1.0
>
>         Attachments: test.cxx
>
>
> The attached test case serializes an invalid XML 1.0 document that contains a character with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters in an XML 1.0 document.
> I've done some digging and it seems that XMLFormatter should check for this. In fast, there is already code for XML 1.1 that checks for these control characters since they need to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0 mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

    [ https://issues.apache.org/jira/browse/XERCESC-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773454#action_12773454 ]

Boris Kolpackov commented on XERCESC-1854:
------------------------------------------

See also XERCESC-1270

> Serialization does not detect invalid XML characters
> ----------------------------------------------------
>
>                 Key: XERCESC-1854
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1854
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: DOM
>    Affects Versions: 3.0.1
>            Reporter: Boris Kolpackov
>             Fix For: 3.1.0
>
>         Attachments: test.cxx
>
>
> The attached test case serializes an invalid XML 1.0 document that contains a character with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters in an XML 1.0 document.
> I've done some digging and it seems that XMLFormatter should check for this. In fast, there is already code for XML 1.1 that checks for these control characters since they need to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0 mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

     [ https://issues.apache.org/jira/browse/XERCESC-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boris Kolpackov updated XERCESC-1854:
-------------------------------------

    Fix Version/s:     (was: 3.1.0)
                   4.0.0
                   3.2.0

Rescheduling for 3.2.0/4.0.0.

> Serialization does not detect invalid XML characters
> ----------------------------------------------------
>
>                 Key: XERCESC-1854
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1854
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: DOM
>    Affects Versions: 3.0.1
>            Reporter: Boris Kolpackov
>             Fix For: 3.2.0, 4.0.0
>
>         Attachments: test.cxx
>
>
> The attached test case serializes an invalid XML 1.0 document that contains a character with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters in an XML 1.0 document.
> I've done some digging and it seems that XMLFormatter should check for this. In fast, there is already code for XML 1.1 that checks for these control characters since they need to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0 mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...