| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in W3C High Resolution Time API. It has been rated as critical. Affected by this issue is some unknown functionality of the component Javascript Handler. The manipulation leads to 7pk time and state. This vulnerability is uniquely identified as CVE-2017-5928. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in W3C High Resolution Time API (Automation Software) (version unknown). It has been rated as critical. This issue affects an unknown function of the component Javascript Handler. The manipulation with an unknown input leads to a 7pk time and state vulnerability. Using CWE to declare the problem leads to CWE-361. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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 even with the https://bugzilla.mozilla.org/show_bug.cgi?id=1167489#c9 protection mechanism in place, which makes it easier for remote attackers to conduct AnC attacks via crafted JavaScript code.
The bug was discovered 02/27/2017. The weakness was disclosed 02/27/2017 (Website). It is possible to read the advisory at cs.vu.nl. The identification of this vulnerability is CVE-2017-5928 since 02/07/2017. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97036†). The entries VDB-97304, VDB-97305 and VDB-97306 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.7
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: 7pk time and stateCWE: CWE-361
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/07/2017 🔍02/27/2017 🔍
02/27/2017 🔍
02/27/2017 🔍
02/27/2017 🔍
02/27/2017 🔍
09/02/2020 🔍
Sources
Advisory: cs.vu.nlStatus: Not defined
CVE: CVE-2017-5928 (🔍)
GCVE (CVE): GCVE-0-2017-5928
GCVE (VulDB): GCVE-100-97307
SecurityFocus: 97036 - W3C High Resolution Time API CVE-2017-5928 Security Vulnerability
OSVDB: - CVE-2017-5928 - W3C High Resolution Time API - AnC Attack Issue
See also: 🔍
Entry
Created: 02/27/2017 21:06Updated: 09/02/2020 15:02
Changes: 02/27/2017 21:06 (59), 09/02/2020 15:02 (4)
Complete: 🔍
Cache ID: 216:1F4:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.