{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1200 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1200 is a low-severity vulnerability in IBM BigFix Compliance, published on 5 Feb 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-2017-1200 and fix it if it is affected.\n\nWhat it is: CVE-2017-1200 is a low-severity vulnerability in IBM BigFix Compliance, published on 5 Feb 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-2017-1200 in the wild and no public exploit code.\n\nAffected product: IBM BigFix Compliance. 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-2017-1200/ (Markdown: https://insights.sbomify.com/CVE-2017-1200/index.md)","id":"CVE-2017-1200","markdown":"https://insights.sbomify.com/CVE-2017-1200/index.md","name":"CVE-2017-1200","record":{"aliases":["GHSA-67jr-4gph-p24h"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM BigFix Compliance","requires_auth":"none","summary":"Attackers can perform man-in-the-middle attacks due to improper certificate validation, potentially spoofing trusted entities and intercepting data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"bigfix_compliance","vendor":"ibm"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.0/A:N/AC:H/AV:N/C:L/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"IBM BigFix Compliance 1.7 through 1.9.91 (TEMA SUAv1 SCA SCM) does not validate, or incorrectly validates, a certificate.This weakness might allow an attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack. The software might connect to a malicious host while believing it is a trusted host, or the software might be deceived into accepting spoofed data that appears to originate from a trusted host. IBM X-Force ID: 123675.","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":"Security feature bypass in BigFix Compliance","id":"CVE-2017-1200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in BigFix Compliance Analytics","id":"CVE-2017-1201"},"packages":[],"prev":{"headline":"Cross-site scripting in InfoSphere Master Data Management","id":"CVE-2017-1199"},"products":["BigFix Compliance"],"published":"2019-02-05","related":[{"cvss_score":5.4,"headline":"Cross-site scripting in BigFix Compliance","id":"CVE-2017-1202","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":5.3,"headline":"Information disclosure in BigFix Compliance","id":"CVE-2017-1177","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":3.7,"headline":"Information disclosure in BigFix Compliance","id":"CVE-2017-1198","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["IBM"]},"summary":"Attackers can perform man-in-the-middle attacks due to improper certificate validation, potentially spoofing trusted entities and intercepting data.","url":"https://insights.sbomify.com/CVE-2017-1200/"}