This repository has been archived by the owner on Apr 15, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 87
Security issue #38
Comments
Hello @lirantal, May i can fix and provide an PR |
Yes @roest01, please check your inbox for the invite |
roest01
added a commit
to roest01/node-pdf-image
that referenced
this issue
May 13, 2018
…6.1) - fix mooz#38 - solution for v2
roest01
added a commit
to roest01/node-pdf-image
that referenced
this issue
May 15, 2018
…6.1) - fix mooz#38 - solution for v2
roest01
added a commit
to roest01/node-pdf-image
that referenced
this issue
May 17, 2018
…6.1) - fix mooz#38 - solution for v2
roest01
added a commit
to roest01/node-pdf-image
that referenced
this issue
Jul 10, 2018
…6.1) - fix mooz#38 - solution for v2
Any news about this issue? |
PR is made. Issue is fixed there ... |
As long as there is no new version how can I sanitize input for the current 2.0.0 version? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I'm a member of the Node.js Security WG and we received a report regarding a security issue with this module. We tried inviting the author by e-mail but received no response so I'm opening this issue and inviting anyone with commit and npm publish rights to collaborate with us on a fix.
The text was updated successfully, but these errors were encountered: