Skip to content
This repository has been archived by the owner on Apr 15, 2020. It is now read-only.

Security issue #38

Open
lirantal opened this issue May 11, 2018 · 6 comments
Open

Security issue #38

lirantal opened this issue May 11, 2018 · 6 comments

Comments

@lirantal
Copy link

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.

@roest01
Copy link
Contributor

roest01 commented May 12, 2018

Hello @lirantal,
you can contact me because of this issue via [anonymized]

May i can fix and provide an PR

@lirantal
Copy link
Author

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
roest01 added a commit to roest01/node-pdf-image that referenced this issue May 15, 2018
roest01 added a commit to roest01/node-pdf-image that referenced this issue May 17, 2018
roest01 added a commit to roest01/node-pdf-image that referenced this issue Jul 10, 2018
@queval-j
Copy link

queval-j commented Apr 4, 2019

Any news about this issue?

@roest01
Copy link
Contributor

roest01 commented Apr 4, 2019

PR is made. Issue is fixed there ...

@roest01
Copy link
Contributor

roest01 commented Apr 16, 2019

Maybe someone or some could do a code review of #39 to help @mooz merging this ?

@svrnwnsch
Copy link

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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants