Vulnerability Database · npm · mock2easy · Version
mock2easy 0.0.17
0.0.17 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 24 Nov 2015
Also known from other sources 1
Newer releases 23
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
mock2easy 0.0.17 vulnerabilities
1 vulnerability cover mock2easy 0.0.17. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7697: Code injection in mock2easy | 9.8 critical | No fix published | 06 May 2021 |
Looking for another version, or everything Vulert holds for mock2easy?
Questions
About mock2easy 0.0.17
Is mock2easy 0.0.17 vulnerable?
Yes. 1 vulnerability in the Vulert database cover mock2easy 0.0.17: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.17 the latest release of mock2easy?
No. 0.0.17 was published 24 Nov 2015, 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 mock2easy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mock2easy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.