We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz
Path to dependency file: /tmp/ws-scm/WebGoat/docs/package.json
Path to vulnerable library: /tmp/ws-scm/WebGoat/docs/node_modules/node-sass/package.json
Dependency Hierarchy:
Found in HEAD commit: 03ef13fd3d7830113ef6f26e7405a340c29ca5c1
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::parenthese_scope in prelexer.hpp.
Publish Date: 2019-01-14
URL: CVE-2019-6283
Base Score Metrics:
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6284
Release Date: 2019-08-06
Fix Resolution: LibSass - 3.6.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
CVE-2019-6283 - Medium Severity Vulnerability
Vulnerable Libraries - node-sass-4.11.0.tgz
node-sass-4.11.0.tgz
Wrapper around libsass
Library home page: https://registry.npmjs.org/node-sass/-/node-sass-4.11.0.tgz
Path to dependency file: /tmp/ws-scm/WebGoat/docs/package.json
Path to vulnerable library: /tmp/ws-scm/WebGoat/docs/node_modules/node-sass/package.json
Dependency Hierarchy:
Found in HEAD commit: 03ef13fd3d7830113ef6f26e7405a340c29ca5c1
Vulnerability Details
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::parenthese_scope in prelexer.hpp.
Publish Date: 2019-01-14
URL: CVE-2019-6283
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6284
Release Date: 2019-08-06
Fix Resolution: LibSass - 3.6.0
The text was updated successfully, but these errors were encountered: