High Resolution Time Api
Vendor:
First CVE: Feb 27, 2017 · Active for 9 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
3.7
Avg CVSS
Higher Avg CVSS than 2% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact High Resolution Time Api over time
Volume of CVEsAvg CVSS Base Score
First CVE
Feb 27, 2017
9 years ago
Most Recent CVE
Feb 27, 2017
3,434 days ago
CVE Severity & Scoring
High Resolution Time Api1 CVEs
100%
All CVEs352,294 CVEs
45%
40%
11%
Low
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High1 (100.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 |
|---|---|---|---|---|---|
The W3C High Resolution Time API, as implemented in various web browsers, does not consider that memory-reference times can be measured by a performance.now "Time to Tick" approach | Feb 27, 2017 | 3.7 | 13 | 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 High Resolution Time Api
Versions
No cataloged versions.