docs/security.xml - xerces-j - Git at Google

 <?xml version='1.0' encoding='UTF-8'?>
 <!--
  * Licensed to the Apache Software Foundation (ASF) under one or more
  * contributor license agreements.  See the NOTICE file distributed with
  * this work for additional information regarding copyright ownership.
  * The ASF licenses this file to You under the Apache License, Version 2.0
  * (the "License"); you may not use this file except in compliance with
  * the License.  You may obtain a copy of the License at
  *
  *      http://www.apache.org/licenses/LICENSE-2.0
  *
  * Unless required by applicable law or agreed to in writing, software
  * distributed under the License is distributed on an "AS IS" BASIS,
  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  * See the License for the specific language governing permissions and
  * limitations under the License.
 -->
 <!DOCTYPE s1 SYSTEM 'dtd/document.dtd'>
 <s1 title="Security">
 <s2 title="Security Model">

 By default, Xerces does what the XML specifications require. In some cases, this may not be appropriate behavior when working with untrusted input. There are multiple methods for blocking access to external entities and for disallowing DOCTYPE declarations, and it is up to the downstream user of Xerces-J to block/reject these constructs where appropriate.

 </s2>
 <s2 title="Reporting">

 <p>
 If you think you have found a security issue in Apache Xerces, please follow the <jump href='https://security.apache.org/report-code'>reporting guidelines</jump>.
 </p>
 <p>
 Results from source code security analyzers are not accepted without additional analysis showing that the problem indeed violates the project's security model, as such tools commonly produce many false positives.
 </p>

 </s2>
 <s2 title="CVE-2017-7503">
 <p>
 In 2017, Red Hat published <jump href="https://www.cve.org/CVERecord?id=CVE-2017-7503">CVE-2017-7503</jump>.
 Note that they do not mark Xerces as affected, only their own 'JBoss Enterprise Application Platform'.
 Sadly, the exact specifics of the issue appear to have been lost to time.
 It looks like it's simply describing that options for features like loading external entities and DTDs are enabled by default, which we (as documented above) consider expected and well-known behavior.
 Possibly JBoss did not correctly take this into account at the time.
 </p>
 </s2>
 </s1>
	<?xml version='1.0' encoding='UTF-8'?>
	<!--
	* Licensed to the Apache Software Foundation (ASF) under one or more
	* contributor license agreements. See the NOTICE file distributed with
	* this work for additional information regarding copyright ownership.
	* The ASF licenses this file to You under the Apache License, Version 2.0
	* (the "License"); you may not use this file except in compliance with
	* the License. You may obtain a copy of the License at
	*
	* http://www.apache.org/licenses/LICENSE-2.0
	*
	* Unless required by applicable law or agreed to in writing, software
	* distributed under the License is distributed on an "AS IS" BASIS,
	* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	* See the License for the specific language governing permissions and
	* limitations under the License.
	-->
	<!DOCTYPE s1 SYSTEM 'dtd/document.dtd'>
	<s1 title="Security">
	<s2 title="Security Model">

	By default, Xerces does what the XML specifications require. In some cases, this may not be appropriate behavior when working with untrusted input. There are multiple methods for blocking access to external entities and for disallowing DOCTYPE declarations, and it is up to the downstream user of Xerces-J to block/reject these constructs where appropriate.

	</s2>
	<s2 title="Reporting">

	<p>
	If you think you have found a security issue in Apache Xerces, please follow the <jump href='https://security.apache.org/report-code'>reporting guidelines</jump>.
	</p>
	<p>
	Results from source code security analyzers are not accepted without additional analysis showing that the problem indeed violates the project's security model, as such tools commonly produce many false positives.
	</p>

	</s2>
	<s2 title="CVE-2017-7503">
	<p>
	In 2017, Red Hat published <jump href="https://www.cve.org/CVERecord?id=CVE-2017-7503">CVE-2017-7503</jump>.
	Note that they do not mark Xerces as affected, only their own 'JBoss Enterprise Application Platform'.
	Sadly, the exact specifics of the issue appear to have been lost to time.
	It looks like it's simply describing that options for features like loading external entities and DTDs are enabled by default, which we (as documented above) consider expected and well-known behavior.
	Possibly JBoss did not correctly take this into account at the time.
	</p>
	</s2>
	</s1>