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
mend-bolt-for-githubbot
changed the title
WS-2019-0310 (High) detected in https-proxy-agent-2.2.2.tgz
WS-2019-0310 (High) detected in https-proxy-agent-2.2.2.tgz - autoclosed
Oct 1, 2021
✔️ 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.
mend-bolt-for-githubbot
changed the title
WS-2019-0310 (High) detected in https-proxy-agent-2.2.2.tgz - autoclosed
WS-2019-0310 (High) detected in https-proxy-agent-2.2.2.tgz
Apr 17, 2022
ℹ️ This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.
ℹ️ This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.
WS-2019-0310 - High Severity Vulnerability
Vulnerable Library - https-proxy-agent-2.2.2.tgz
An HTTP(s) proxy `http.Agent` implementation for HTTPS
Library home page: https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-2.2.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in HEAD commit: a1c271764655c7e3ff81126d5929b8dda6170bf4
Found in base branch: datasource-meta
Vulnerability Details
"in 'https-proxy-agent', before v2.2.3, there is a failure of TLS enforcement on the socket. Attacker may intercept unencrypted communications.
Publish Date: 2019-10-07
URL: WS-2019-0310
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/1184
Release Date: 2019-10-07
Fix Resolution: https-proxy-agent - 2.2.3
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: