-
Notifications
You must be signed in to change notification settings - Fork 34
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
Security issue: Downloads Resources over HTTP #27
Comments
There does not appear to be an https version of the unicode data URL. Would you be willing to include an offline copy of the data in the package, fetched at publish time? |
put the dowbload code in a prepublish/build script and add the file to your package |
@HansHammel That solution requires every user of this package to do unnecessary extra work. Let's solve it once, correctly, in this package so that all users aren't exposed to man-in-middle attacks because of insecure http requests. |
as I said, put the file in the code |
@HansHammel I think you're either trolling me, or just misunderstanding what I wrote. I suggest rereading this thread before commenting further. @dodo Any thoughts on this issue? Would you accept a PR that downloads UnicodeData.txt at publish time and includes it in this package? This would resolve the outstanding Node.js Security Advisory against this package. |
No, seriously, why do you have to download the file? Is there any reason you cannot embed it and update it only on new package releases (publish)!? Do it like those guys or use their link (trustworthy!?) https://github.com/latex3/unicode-data/blob/master/UnicodeData.txt |
@HansHammel You're advocating for the same thing that I am. Download the file right before a release. |
Any advancement on that? I can't push my project into production if there's a security flaw, as our CI runs As it uses this package, it would be great to have a definitive solution… |
https coming soon |
If it will be loaded over HTTPS, it is still an issue if the unicode server goes down or throttles downloads as discussed in #25 and other issues in this repo. Especially on Mac OS, where you can't simply |
Moreover sourceforge is far from reliable. Store this file directly in the module is the best way to avoid problems and improve human validation. |
Hi, I just created a pull request, doing this, as we have the same issue: #28 I'd by happy about any reviews ;) We at eversports.com also depend on quite some packages using this one and at the moment it breaks our development and deployment processes. I also just wrote to the npmjs support team about this, because the package seems quite orphaned. If someone wants to join maintaining the package, please don't hesitate getting in touch with me. I hope I'll get a quick response from the npmjs team. We'll see... |
/popcorn |
adding
seems to help if you're on travis-ci |
Hello everyone! I just published a new version on npm and thereby directly adopted the unicode version scheme, so the new version is 9.0.0. The slug package should automatically use this new version. You find the new fork here: https://github.com/eversport/node-unicodetable Feel free to create or move any issues there! Also, anyone who wants to join maintaining or just create new pull requests is very welcome! The new version also provides the category/*.js files directly, so there is no need to download a file from unicode.org anymore during install. |
@tdanecker also see #16 |
There is currently an open security advisory about this module from the Node Security Project.
https://nodesecurity.io/advisories/161
Overview
unicode loads unicode data downloaded from unicode.org into nodejs.
Unicode downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks.
Remediation
No fix is currently available for this vulnerability.
It is our recommendation to not install or use this module at this time.
The text was updated successfully, but these errors were encountered: