Skip to content

Use Safe Parsers in lxml Parsing Functions#27

Open
pixeebot[bot] wants to merge 1 commit intomasterfrom
pixeebot/drip-2024-05-31-pixee-python/safe-lxml-parsing
Open

Use Safe Parsers in lxml Parsing Functions#27
pixeebot[bot] wants to merge 1 commit intomasterfrom
pixeebot/drip-2024-05-31-pixee-python/safe-lxml-parsing

Conversation

@pixeebot
Copy link

@pixeebot pixeebot bot commented May 31, 2024

This codemod sets the parser parameter in calls to lxml.etree.parse and lxml.etree.fromstring if omitted or set to None (the default value). Unfortunately, the default parser=None means lxml will rely on an unsafe parser, making your code potentially vulnerable to entity expansion attacks and external entity (XXE) attacks.

The changes look as follows:

  import lxml.etree
- lxml.etree.parse("path_to_file")
- lxml.etree.fromstring("xml_str")
+ lxml.etree.parse("path_to_file", parser=lxml.etree.XMLParser(resolve_entities=False))
+ lxml.etree.fromstring("xml_str", parser=lxml.etree.XMLParser(resolve_entities=False))
More reading

I have additional improvements ready for this repo! If you want to see them, leave the comment:

@pixeebot next

... and I will open a new PR right away!

🧚🤖 Powered by Pixeebot

💬Feedback | 👥Community | 📚Docs | Codemod ID: pixee:python/safe-lxml-parsing

@pixeebot
Copy link
Author

pixeebot bot commented Jun 8, 2024

I'm confident in this change, and the CI checks pass, too!

If you see any reason not to merge this, or you have suggestions for improvements, please let me know!

@pixeebot
Copy link
Author

pixeebot bot commented Jun 9, 2024

Just a friendly ping to remind you about this change. If there are concerns about it, we'd love to hear about them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants