Vulnerability Database · npm · st · Version
st 0.0.2
0.0.2 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 1 Low 0 Unrated 0
-
Released 11 Aug 2012
Status deprecated release
Licence non-standard
Also known from other sources 2
Newer releases 54
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
st 0.0.2 vulnerabilities
2 vulnerabilities cover st 0.0.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2014-3744: Directory Traversal in st | 7.5 high | 0.2.5 | 31 Aug 2020 |
| CVE-2017-16224: Open Redirect in st | 6.1 medium | 1.2.2 | 06 Aug 2018 |
Looking for another version, or everything Vulert holds for st?
Questions
About st 0.0.2
Is st 0.0.2 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover st 0.0.2: 0 critical, 1 high, 1 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.2 the latest release of st?
No. 0.0.2 was published 11 Aug 2012, 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 st for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the st version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.