{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5928 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5928 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5928 is a low-severity vulnerability in n/a, published on 27 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-5928 and fix it if it is affected.\n\nWhat it is: CVE-2017-5928 is a low-severity vulnerability in n/a, published on 27 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-5928 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-5928/ (Markdown: https://insights.sbomify.com/CVE-2017-5928/index.md)","id":"CVE-2017-5928","markdown":"https://insights.sbomify.com/CVE-2017-5928/index.md","name":"CVE-2017-5928","record":{"aliases":["GHSA-3m9f-698w-3mf8"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Web Browser","requires_auth":"none","summary":"Remote attackers can exploit timing side-channels in browser APIs to leak sensitive memory information via crafted JavaScript.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"high_resolution_time_api","vendor":"w3"}],"cvss":{"score":3.7,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2017-5928","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"QOS.ch Logback vulnerable to Deserialization of Untrusted Data","id":"CVE-2017-5929"},"packages":[],"prev":{"headline":"Page table walks conducted by the MMU during virtual to physical address translation leave a trace in the last level cache of modern ARM processors.","id":"CVE-2017-5927"},"products":["n/a"],"published":"2017-02-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can exploit timing side-channels in browser APIs to leak sensitive memory information via crafted JavaScript.","url":"https://insights.sbomify.com/CVE-2017-5928/"}