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.

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

arrayfire-js security issue #14

Open
pavanky opened this issue Jul 6, 2018 · 5 comments
Open

arrayfire-js security issue #14

pavanky opened this issue Jul 6, 2018 · 5 comments

Comments

@pavanky
Copy link
Member

pavanky commented Jul 6, 2018

@unbornchikken
Can you look into fixing this https://nvd.nist.gov/vuln/detail/CVE-2016-10598 ?

@unbornchikken
Copy link
Member

I don't get it. There is nothing to get donwloaded by ArrayFire.js itself. NPM downloads the module from the registry during the installation but it's part of the very standard Node.js module infrastructure. For the build process CMake.js downloads headers and lib files but it's been using https urls only, please refer to this file: https://github.com/cmake-js/cmake-js/blob/master/lib/es6/runtimePaths.js.

@pavanky
Copy link
Member Author

pavanky commented Jul 9, 2018

@unbornchikken looks like the CVE is from 2016? but it only got published recently. I am not sure what is happening :-/

@pavanky
Copy link
Member Author

pavanky commented Jul 9, 2018

Looks like this is the original report: https://nodesecurity.io/advisories/192

@p3x-robot
Copy link

this is funny :)

@p3x-robot
Copy link

arrayfire-js security issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants