Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't load external entity from xmlSAX2GetEntity
Despite the comment, I can't see a reason why external entities must be loaded in the SAX handler. For external entities, the handler is typically first invoked via xmlParseReference which will later load the entity on its own if it wasn't loaded yet. The old code also lead to duplicated SAX events which makes it basically impossible to reuse xmlSAX2GetEntity for a custom SAX parser. See the change to the expected test output. Note that xmlSAX2GetEntity was loading the entity via xmlParseCtxtExternalEntity while xmlParseReference uses xmlParseExternalEntityPrivate. In the previous commit, the two functions were merged, trying to compensate for some slight differences between the two mostly identical implementations. But the more urgent reason for this change is that xmlParseReference has the facility to abort early when recursive entities are detected, avoiding what could practically amount to an infinite loop. If you want to backport this change, note that the previous three commits are required as well: f9ea1a2 Fix copying of entities in xmlParseReference 5c7e0a9 Copy some XMLReader option flags to parser context 1a3e584 Merge code paths loading external entities Found by OSS-Fuzz.
- Loading branch information