{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45181 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45181 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45181 is a high-severity memory corruption vulnerability in n/a, published on 12 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45181 and fix it if it is affected.\n\nWhat it is: CVE-2024-45181 is a high-severity memory corruption vulnerability in n/a, published on 12 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45181 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-45181/ (Markdown: https://insights.sbomify.com/CVE-2024-45181/index.md)","id":"CVE-2024-45181","markdown":"https://insights.sbomify.com/CVE-2024-45181/index.md","name":"CVE-2024-45181","record":{"aliases":["GHSA-f2jx-jjc7-hv9g"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WibuKey driver","requires_auth":"low_privilege","summary":"Crafted packets trigger arbitrary address writes in the WibuKey kernel driver, enabling memory corruption and potential privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wibukey","vendor":"wibu"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in WibuKey64.sys in WIBU-SYSTEMS WibuKey before v6.70 and fixed in v.6.70. An improper bounds check allows crafted packets to cause an arbitrary address write, resulting in kernel memory corruption.","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":"Memory corruption in n/a","id":"CVE-2024-45181","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-45182"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-45180"},"products":["n/a"],"published":"2024-09-12","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2018-3990","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":8.5,"headline":"WibuKey Runtime 6.51 - 'WkSvW32.exe' Unquoted Service Path","id":"CVE-2021-47810","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2024-45182","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":4.3,"headline":"Information disclosure in n/a","id":"CVE-2018-3989","kev_date_added":null,"published":"2019-02-05"}],"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":"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-09-12","vendors":["n/a"]},"summary":"Crafted packets trigger arbitrary address writes in the WibuKey kernel driver, enabling memory corruption and potential privilege escalation.","url":"https://insights.sbomify.com/CVE-2024-45181/"}