W3 High Resolution Time Api -
Approved changes feed: RSS · Atom
cpe:2.3:a:w3:high_resolution_time_api:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | W3 (11b4484f-87c5-5c4d-9d38-333439abc844) |
|---|---|
| Product | High Resolution Time Api (e0ba87ca-d297-50ed-9df8-87c4d132abfd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/w3c/hr-time |
purl2cpe | 2026-06-01 10:17:39.837409 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-5928 |
vulnerable | 2026-06-08 05:09:50.118787 |
Details available
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.
Published: 2017-02-27T07:25:00.000Z
Updated: 2024-08-05T15:18:48.372Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.