{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3989 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3989 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3989 is a medium-severity vulnerability in n/a, published on 5 Feb 2019. 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-2018-3989 and fix it if it is affected.\n\nWhat it is: CVE-2018-3989 is a medium-severity vulnerability in n/a, published on 5 Feb 2019. 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-2018-3989 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-2018-3989/ (Markdown: https://insights.sbomify.com/CVE-2018-3989/index.md)","id":"CVE-2018-3989","markdown":"https://insights.sbomify.com/CVE-2018-3989/index.md","name":"CVE-2018-3989","record":{"aliases":["GHSA-r77m-fr9v-2jvr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WibuKey kernel driver","requires_auth":"none","summary":"A local attacker can trigger a kernel memory disclosure in the WibuKey driver by sending a crafted IRP request, potentially exposing sensitive kernel data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"wibukey","vendor":"wibu"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An exploitable kernel memory disclosure vulnerability exists in the 0x8200E804 IOCTL handler functionality of WIBU-SYSTEMS WibuKey.sys Version 6.40 (Build 2400).A specially crafted IRP request can cause the driver to return uninitialized memory, resulting in kernel memory disclosure. An attacker can send an IRP request to trigger this vulnerability.","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-2018-3989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-3990"},"packages":[],"prev":{"headline":"Information disclosure in Signal","id":"CVE-2018-3988"},"products":["n/a"],"published":"2019-02-05","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.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45181","kev_date_added":null,"published":"2024-09-12"},{"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"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A local attacker can trigger a kernel memory disclosure in the WibuKey driver by sending a crafted IRP request, potentially exposing sensitive kernel data.","url":"https://insights.sbomify.com/CVE-2018-3989/"}