You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior: Protobuf.js passes all security scans and vulnerability checks.
Actual Behavior: It fails our scans repeatedly because of a known minimatch 3.0.4 (or lower) security vulnerability.
Additional notes: Because of the way the cli is packaged (lock file + node_modules folder), we are unable to cleanse the problem through conventional means. (npm overrides or yarn resolutions for instance). We do not use the CLI for production runtimes, but because of the way protobufjs is packaged, the cli and its vulnerability end up in the production image.
The text was updated successfully, but these errors were encountered:
diomedtmc
changed the title
minimatch security vulnerable in CLI - only way to fix it is to delete cli folder
minimatch security vulnerability in CLI - only way to fix it is to delete cli folder
Mar 16, 2022
diomedtmc
changed the title
minimatch security vulnerability in CLI - only way to fix it is to delete cli folder
minimatch security vulnerability in CLI - only way to fix it is to delete cli folder contents
Mar 16, 2022
If I follow this, glob packages minimatch. Minimatch released a fix, glob also has a newer build, picking this up should pick up that.
Fixesprotobufjs#1696Fixesprotobufjs#1697Fixesprotobufjs#1698
* Patch minimatch vulnerability
If I follow this, glob packages minimatch. Minimatch released a fix, glob also has a newer build, picking this up should pick up that.
Fixes#1696Fixes#1697Fixes#1698
* chore: update lockfile
Co-authored-by: Alexander Fenster <fenster@google.com>
protobuf.js version: 6.11.2
Expected Behavior: Protobuf.js passes all security scans and vulnerability checks.
Actual Behavior: It fails our scans repeatedly because of a known minimatch 3.0.4 (or lower) security vulnerability.
Additional notes: Because of the way the cli is packaged (lock file + node_modules folder), we are unable to cleanse the problem through conventional means. (npm overrides or yarn resolutions for instance). We do not use the CLI for production runtimes, but because of the way protobufjs is packaged, the cli and its vulnerability end up in the production image.
The text was updated successfully, but these errors were encountered: