Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-656

jaxrpc xml parser can introduce corruption in the output when parsing

    XMLWordPrintable

    Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Express8, Snapshot9, Snapshot9.5, Snapshot9.5.1, Snapshot9.5.2_RC1, Snapshot9.5.2, 9.5.3_RC1
    • 9.5.3, 10.0.0-EA
    • web services
    • Rank:
      1|hzn9kv:

      Description

      If you have some XML like this coming in from the IDM/SMS remote APIs.

      <item xsi:type="ns1:mapEntry">
      <key xsi:type="xsd:string">com.sun.identity.agents.config.notenforced.uri</key>
      <value xsi:type="ns1:hashSet" enc:arrayType="xsd:anyType[1]">
      <item xsi:type="xsd:string">[0]=</item>
      </value>
      </item>

      then the data; [0]= actually becomes [[0]= and will fail validation. This is due to a bug in JAXRPC. JAXRPC uses a 2k buffer to process the XML and if the end of the buffer ends up like this:

      <item xsi:type="ns1:mapEntry"><key xsi:type="xsd:string">com.sun.identity.agents.config.bypass.principal</key><value xsi:type="ns1:hashSet" enc:arrayType="xsd:anyType[1]"><item xsi:type="xsd:string">[0]=</item></value></item><item xsi:type="ns1:mapEntry"><key xsi:type="xsd:string">com.sun.identity.agents.config.notenforced.uri</key><value xsi:type="ns1:hashSet" enc:arrayType="xsd:anyType[1]"><item xsi:type="xsd:string">[0]

      Where the value spans the buffer boundary then the bug will include the character twice.

      This is bug JAX_RPC-48 in the JAX RPC project.

        Attachments

          Issue Links

            Activity

              People

              steve Steve Ferris
              steve Steve Ferris
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: