-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
WS-2019-0540 (Medium) detected in autolinker-0.28.1.tgz - autoclosed #3112
Comments
✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory. |
Thank you for your report, the issue you have reported has just been fixed.
|
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://github.com/AlexRogalskiy/java-patterns/blob/master/.github/ISSUE_TEMPLATE/bug_report.md), and link to this old issue if necessary. |
WS-2019-0540 - Medium Severity Vulnerability
Vulnerable Library - autolinker-0.28.1.tgz
Utility to automatically link the URLs, email addresses, and Twitter handles in a given block of text/HTML
Library home page: https://registry.npmjs.org/autolinker/-/autolinker-0.28.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/autolinker/package.json
Dependency Hierarchy:
Found in HEAD commit: fe3fc69c6aa9128d2a4b77ebfd8d8e355574dd05
Found in base branch: master
Vulnerability Details
Denial of Service (DoS) vulnerability was found in autolinker before 3.0.0. Unterminated img src causes long execution.
Publish Date: 2019-01-08
URL: WS-2019-0540
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://github.com/gregjacobs/Autolinker.js/releases/tag/v3.0.0
Release Date: 2019-01-08
Fix Resolution: autolinker - 3.0.0
Step up your Open Source Security Game with WhiteSource here
The text was updated successfully, but these errors were encountered: