{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-31498 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31498 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31498 is a high-severity vulnerability in n/a, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-31498 and fix it if it is affected.\n\nWhat it is: CVE-2024-31498 is a high-severity vulnerability in n/a, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-31498 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-2024-31498/ (Markdown: https://insights.sbomify.com/CVE-2024-31498/index.md)","id":"CVE-2024-31498","markdown":"https://insights.sbomify.com/CVE-2024-31498/index.md","name":"CVE-2024-31498","record":{"aliases":["GHSA-5h4m-75jp-hg7m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"YubiKey Manager GUI","requires_auth":"low_privilege","summary":"Attackers can escalate privileges by opening browser windows as Administrator in YubiKey Manager GUI on Windows when Edge is not used.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Yubico ykman-gui (aka YubiKey Manager GUI) before 1.2.6 on Windows, when Edge is not used, allows privilege escalation because browser windows can open as Administrator.","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":"Privilege escalation in n/a","id":"CVE-2024-31498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-31502"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2024-31497"},"products":["n/a"],"published":"2024-04-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-27","vendors":["n/a"]},"summary":"Attackers can escalate privileges by opening browser windows as Administrator in YubiKey Manager GUI on Windows when Edge is not used.","url":"https://insights.sbomify.com/CVE-2024-31498/"}