{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20812 is a high-severity vulnerability in n/a, published on 16 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20812 and fix it if it is affected.\n\nWhat it is: CVE-2018-20812 is a high-severity vulnerability in n/a, published on 16 Mar 2019. 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-2018-20812 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-20812/ (Markdown: https://insights.sbomify.com/CVE-2018-20812/index.md)","id":"CVE-2018-20812","markdown":"https://insights.sbomify.com/CVE-2018-20812/index.md","name":"CVE-2018-20812","record":{"aliases":["GHSA-64wp-r983-gxp4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Pulse Secure Desktop","requires_auth":"none","summary":"Attackers can intercept IPv6 DNS traffic bypassing the VPN tunnel on dual-stack endpoints when Traffic Enforcement is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pulse_secure_desktop_client","vendor":"pulsesecure"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information exposure issue where IPv6 DNS traffic would be sent outside of the VPN tunnel (when Traffic Enforcement was enabled) exists in Pulse Secure Pulse Secure Desktop 9.0R1 and below. This is applicable only to dual-stack (IPv4/IPv6) endpoints.","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-20812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2018-20813"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-20811"},"products":["n/a"],"published":"2019-03-16","related":[{"cvss_score":9.8,"headline":"Privilege escalation in Pulse Secure Desktop Cient","id":"CVE-2020-8239","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":8.8,"headline":"Path traversal in Pulse Secure Desktop Client","id":"CVE-2020-8254","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8240","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8248","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Memory corruption in Pulse Secure Desktop Client","id":"CVE-2020-8249","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8250","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-15865","kev_date_added":null,"published":"2018-09-06"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can intercept IPv6 DNS traffic bypassing the VPN tunnel on dual-stack endpoints when Traffic Enforcement is enabled.","url":"https://insights.sbomify.com/CVE-2018-20812/"}