-
Notifications
You must be signed in to change notification settings - Fork 181
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
Vulnerability: Misinterpretation of malicious XML input #203
Comments
|
xmldom could not be updated due to missing permissions. The proposed solution is to switch to the @xmldom/xmldom Refs: xmldom/xmldom#278 xmldom/xmldom#271 |
@putermancer Could you please take a look in to this? |
Resolved in recently merged PR. |
@larrymyers Could you please publish a version with this fix? |
Do you mean #205? I believe this fix is not correct, xmldom does not have a version 0.7.0. It was moved to @xmldom/xmldom, where the latest version is 0.7.3 currently. I had sent some links in my comment above about the background of this move. I created new PR #206 to fix the issue. Shall we re-open this issue until new jasmine-reporters version is published? |
Per this advisory, it seems that it's recommended that a version of xmldom >= 0.5.0 is used instead.
I came upon this when running npm install for a project that currently utilizes JUnitXMLReporter of this package.
The text was updated successfully, but these errors were encountered: