{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-0210 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2015-0210 is a medium-severity vulnerability in n/a, published on 28 Aug 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-2015-0210 and fix it if it is affected.\n\nWhat it is: CVE-2015-0210 is a medium-severity vulnerability in n/a, published on 28 Aug 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-2015-0210 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-2015-0210/ (Markdown: https://insights.sbomify.com/CVE-2015-0210/index.md)","id":"CVE-2015-0210","markdown":"https://insights.sbomify.com/CVE-2015-0210/index.md","name":"CVE-2015-0210","record":{"aliases":["GHSA-4vg4-q9rf-r94r","SUSE-SU-2018:1659-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"wpa_supplicant","requires_auth":"none","summary":"Attackers can perform man-in-the-middle attacks due to improper certificate subject name validation in wpa_supplicant.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"wpa_supplicant","vendor":"w1.fi"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"wpa_supplicant 2.0-16 does not properly check certificate subject name, which allows remote attackers to cause a man-in-the-middle attack.","ecosystems":["SUSE:Linux Enterprise Server 11 SP4","SUSE:Linux Enterprise Server for SAP Applications 11 SP4"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2015-0210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":2,"n_references":2,"next":{"headline":"Moodle allows attackers to obtain sensitive information","id":"CVE-2015-0211"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Server 11 SP4","fixed":["0.7.1-6.18.6.1"],"introduced":["0"],"last_affected":[],"package":"wpa_supplicant","purl":"pkg:rpm/suse/wpa_supplicant\u0026distro=SUSE%20Linux%20Enterprise%20Server%2011%20SP4","source":"SUSE-SU-2018:1659-1"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","fixed":["0.7.1-6.18.6.1"],"introduced":["0"],"last_affected":[],"package":"wpa_supplicant","purl":"pkg:rpm/suse/wpa_supplicant\u0026distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2011%20SP4","source":"SUSE-SU-2018:1659-1"}],"prev":{"headline":"Use after free in n/a","id":"CVE-2015-0209"},"products":["n/a"],"published":"2017-08-28","related":[{"cvss_score":8.8,"headline":"Privilege escalation in wpa supplicant","id":"CVE-2024-5290","kev_date_added":null,"published":"2024-08-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"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-06","vendors":["n/a"]},"summary":"Attackers can perform man-in-the-middle attacks due to improper certificate subject name validation in wpa_supplicant.","url":"https://insights.sbomify.com/CVE-2015-0210/"}