Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Are there any plans to port the fix for CVE-2021-33813 to jdom v1.x? #204

Open
jacalata opened this issue Nov 4, 2022 · 0 comments
Open

Are there any plans to port the fix for CVE-2021-33813 to jdom v1.x? #204

jacalata opened this issue Nov 4, 2022 · 0 comments

Comments

@jacalata
Copy link

jacalata commented Nov 4, 2022

Separating out jdom 1.x to clarify that the CVE has been addressed in 2.x

Original comment:
Are there any plans to port the fix for CVE-2021-33813 to jdom v1.x? We're experiencing issues with Apache Commons JXPath, which is not compatible with jdom v2.x..

Originally posted by @mmkamburova in #189 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacalata