doc: Consider removing dangerous Buffer usage from the Readme
See original GitHub issueI’m talking about the examples on https://github.com/form-data/form-data#usage.
Sending new Buffer(10)
to a remote host is unsafe, it basically sends a chunk of process memory, which potentially cointains db passwords, encryption keys, source file chunks, etc.
While not a vulnerability in form-data
, having that code as the first example of how to use this library is probably not a very good idea.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
@guld/safe-buffer - npm
Use of Buffer.allocUnsafeSlow() should be used only as a last resort after a developer has observed undue memory retention in their applications ...
Read more >User Data Options - ReadMe Documentation
Just wrap the variable name with <<variable>> to user's value, or the default if no value is set. <<name>> will be replaced with...
Read more >base/containers/README.md - chromium/src - Git at Google
efficiently. In this case, consider `base::flat_map` and `base::flat_set`. You need to be aware of the maximum expected size of the container since.
Read more >Changelog — Python 3.11.1 documentation
gh-92888: Fix memoryview use after free when accessing the backing buffer in certain cases. gh-68966: The deprecated mailcap module now refuses to inject...
Read more >ChangeLog - Zlib
configure for Solaris, support --64 [Mooney] - Remove -R. from Solaris shared ... use of Z_BUF_ERROR in gz* functions except for premature EOF...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@motet-a I agree, we should probably remove this deprecated api. I plan on doing some cleanup on this lib when I get a bit of time but feel free to make a PR.
In addition to be unsafe, it is deprecated.