Browserify Hot Module Replacement
Vendor:
First CVE: Sep 21, 2018 · Active for 7 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
7.5
Avg CVSS
Higher Avg CVSS than 50% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Browserify Hot Module Replacement over time
Volume of CVEsAvg CVSS Base Score
First CVE
Sep 21, 2018
7 years ago
Most Recent CVE
Sep 21, 2018
2,864 days ago
CVE Severity & Scoring
Browserify Hot Module Replacement1 CVEs
100%
All CVEs352,427 CVEs
45%
40%
11%
High
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2018-14730HIGH An issue was discovered in Browserify-HMR. Attackers are able to steal developer's code because the origin of requests is not checked by the WebSocket server, which is used for HMR | Sep 21, 2018 | 7.5 | 26 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Browserify Hot Module Replacement
Top CWEs
Versions
No cataloged versions.