-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-127502: Update XML vulnerability table #135294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Python 3.11-3.15 include expat 2.7.1 which is not vulnerable. expat 2.6.0 was released in February 2024.
Do you think the table should be kept, now that it says Safe almost everywhere? |
The table has many notes with pyexpat versions. There are likely old Python versions in the wild with old pyexat versions. The question is more if we need to keep the big red warning at the top:
Maybe this warning can just be removed. Since Python XML modules are now safe by default, we can maybe remove references to the defusedxml project which is no longer needed. Note: The latest defused version (0.7.0) was released in 2021. There is a 0.8.0rc2 version around since September 2023 with no final release. The project seems to be unmaintained (latest commit: 2 years ago). |
I updated my PR to remove the red warning and remove references to defusedxml. |
There are similar warnings in several other files, e.g.:
|
Replace also "XML Vulnerabilities" with "XML Security".
Good catch. I replaced most warnings with notes. I replaced also "XML Vulnerabilities" with "XML Security". I kept the warnings for XML-RPC client and server since the XML table still says that XML-RPC is vulnerable to decompression bomb. |
Python 3.11-3.15 include expat 2.7.1 which is not vulnerable.
expat 2.6.0 was released in February 2024.
📚 Documentation preview 📚: https://cpython-previews--135294.org.readthedocs.build/