Vulnerability Database · npm · rtcmulticonnection-client · Version
rtcmulticonnection-client 1.0.1
1.0.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.5.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 20 Nov 2014
Licence MIT
Also known from other sources 1
Newer releases 6
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
rtcmulticonnection-client 1.0.1 vulnerabilities
1 vulnerability cover rtcmulticonnection-client 1.0.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-16125: Directory Traversal in rtcmulticonnection-client | 7.5 high | No fix published | 23 Jul 2018 |
Looking for another version, or everything Vulert holds for rtcmulticonnection-client?
Questions
About rtcmulticonnection-client 1.0.1
Is rtcmulticonnection-client 1.0.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover rtcmulticonnection-client 1.0.1: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.5, and each entry above names the fixed version to move to.
Which version of rtcmulticonnection-client should I use instead of 1.0.1?
1.0.5 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.0.1 the latest release of rtcmulticonnection-client?
No. 1.0.1 was published 20 Nov 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor rtcmulticonnection-client for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rtcmulticonnection-client version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.