fix(QTDI-1938): Resolving XML external entity in user-controlled data #1106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/Talend/component-runtime/security/code-scanning/30
To fix this XXE vulnerability, ensure that the JAXB
Unmarshaller
is configured to disallow external entity expansion and DTD parsing. The standard mitigation is to set a customXMLInputFactory
/SAXParserFactory
or to use ajavax.xml.stream.XMLStreamReader
orjavax.xml.parsers.SAXParser
with features that disable DTDs and external entities, then pass the result to the JAXBUnmarshaller
. The most portable and concise approach (recommended by OWASP and Oracle) is to use a hardenedSAXSource
, i.e., create aSAXParserFactory
, disable external entities, and create anXMLReader
for the parsing.The concrete change is:
Replace the call to
with
where
xmlReader
is anXMLReader
from aSAXParserFactory
with DTD and external entity handling disabled. This requires importingorg.xml.sax.InputSource
,javax.xml.parsers.SAXParserFactory
, andorg.xml.sax.XMLReader
. Only modifyJAXBDecoder.java
as shown; do not alter howJAXBContext
is managed.Suggested fixes powered by Copilot Autofix. Review carefully before merging.