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

Upgrade xmldom to a non-vulnerable version #111

Closed
filiptronicek opened this issue Aug 19, 2021 · 2 comments
Closed

Upgrade xmldom to a non-vulnerable version #111

filiptronicek opened this issue Aug 19, 2021 · 2 comments

Comments

@filiptronicek
Copy link

The maintainers of the xmldom package had some trouble publishing a security update under the original namespace, so the package now lives at @xmldom/xmldom. More details are in xmldom/xmldom#271. Without updating this, xmldom will still be vulnerable under CVE-2021-32796.
@SudiptaAtWork
Copy link

Any update when plist can point to @xmldom/xmldom?

@dylmye dylmye mentioned this issue Aug 20, 2021
Closed
@mdreier-sap mdreier-sap mentioned this issue Aug 24, 2021
Closed
3 tasks
mreinstein added a commit that referenced this issue Aug 27, 2021
@mreinstein
inline xmldom@0.6.0 to avoid false positive security message. Fixes #110
fa8e184 
, #111
@mreinstein
Copy link
Collaborator

fixed via fa8e184

This was referenced Sep 23, 2021
Closed
Closed
jiansheng-gt pushed a commit to jiansheng-gt/plist.js that referenced this issue Nov 11, 2021
Revert "inline xmldom@0.6.0 to avoid false positive security message. F…
75d7d02 
…ixes TooTallNate#110, TooTallNate#111"

This reverts commit fa8e184.
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

Successfully merging a pull request may close this issue.

Update xmldom to 0.7.x
3 participants
@mreinstein @SudiptaAtWork @filiptronicek