How severe is CVE-2018-16479?

No CVSS score has been assigned to CVE-2018-16479 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2018-16479?

CVE-2018-16479 affects the following packages: http-live-simulator (npm). Ecosystems affected: npm.

How do I fix CVE-2018-16479?

Update http-live-simulator to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16479 is resolved across your whole dependency graph.

How do I detect CVE-2018-16479 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for http-live-simulator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-16479 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2018-16479 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-16479, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-16479?

CVE-2018-16479 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 76th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-16479?

CVE-2018-16479 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-16479 published, and has it been updated?

CVE-2018-16479 was published on February 7, 2019 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2018-16479 — http-live-simulator

CVE-2018-16479 is a Path Traversal vulnerability in http-live-simulator. 1 public exploit reference exists, so weaponization risk is real. A fix is available for http-live-simulator — see the affected versions and patch details below.

Path Traversal in http-live-simulator

Published

Feb 7, 2019

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

http-live-simulatornpm

71downloads / week

Description

Versions of http-live-simulator prior to 1.0.7 are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths. For example: curl --path-as-is http://localhost:8080//../../../../etc/passwd.

Recommendation

Upgrade to version 1.0.7

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`http-live-simulator`	all versions	1.0.7`npm install http-live-simulator@1.0.7`

Affected Products

1 product · 1 configurations

Application

http-live-simulatorhttp-live-simulator_project

≤ 1.0.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Path traversal vulnerability in http-live-simulator <1.0.7 causes unauth…

hackerone.comNVDOct 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for http-live-simulator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update http-live-simulator to 1.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16479 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Versions of `http-live-simulator` prior to 1.0.7 are vulnerable to Path Traversal. Due to insufficient input sanitization, attackers can access server files by using relative paths. For example: `curl --path-as-is http://localhost:8080//../../../../etc/passwd`. ## Recommendation Upgrade to version 1.0.7

O3 Security · Impact-Aware SCA

Is CVE-2018-16479 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works