Vulnerability Database · npm · openssl.js · Version
openssl.js 0.0.2-security
0.0.2-security 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.2.0.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 02 Aug 2017
Licence Apache-2.0
Also known from other sources 1
Newer releases 14
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
openssl.js 0.0.2-security vulnerabilities
1 vulnerability cover openssl.js 0.0.2-security. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-16065: Hijacked Environment Variables in openssl.js | 7.5 high | No fix published | 29 Aug 2018 |
Looking for another version, or everything Vulert holds for openssl.js?
Questions
About openssl.js 0.0.2-security
Is openssl.js 0.0.2-security vulnerable?
Yes. 1 vulnerability in the Vulert database cover openssl.js 0.0.2-security: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.2.0, and each entry above names the fixed version to move to.
Which version of openssl.js should I use instead of 0.0.2-security?
1.2.0 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 0.0.2-security the latest release of openssl.js?
No. 0.0.2-security was published 02 Aug 2017, 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 openssl.js for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the openssl.js version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.