{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-4953 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-4953 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-4953 is a medium-severity vulnerability in n/a, published on 29 Mar 2018. 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-4953 and fix it if it is affected.\n\nWhat it is: CVE-2015-4953 is a medium-severity vulnerability in n/a, published on 29 Mar 2018. 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-4953 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-4953/ (Markdown: https://insights.sbomify.com/CVE-2015-4953/index.md)","id":"CVE-2015-4953","markdown":"https://insights.sbomify.com/CVE-2015-4953/index.md","name":"CVE-2015-4953","record":{"aliases":["GHSA-6q4x-jxmf-pjpx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM BigFix Remote Control","requires_auth":"none","summary":"Man-in-the-middle attackers can decrypt traffic due to a weakness in the encryption protocol of IBM BigFix Remote Control.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"bigfix_remote_control","vendor":"ibm"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"IBM BigFix Remote Control before Interim Fix pack 9.1.2-TIV-IBRC912-IF0001 makes it easier for man-in-the-middle attackers to decrypt traffic by leveraging a weakness in its encryption protocol. IBM X-Force ID: 105197.","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":"Weak cryptography in n/a","id":"CVE-2015-4953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2015"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2015-4954"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2015-4952"},"products":["n/a"],"published":"2018-03-29","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-2944","kev_date_added":null,"published":"2016-11-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-2963","kev_date_added":null,"published":"2016-11-30"},{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2016-2929","kev_date_added":null,"published":"2016-11-25"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-2948","kev_date_added":null,"published":"2016-11-30"},{"cvss_score":7.5,"headline":"Auth bypass in BigFix Remote Control","id":"CVE-2016-2930","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":7.3,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-2936","kev_date_added":null,"published":"2016-11-30"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2016-2933","kev_date_added":null,"published":"2016-11-30"}],"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-06","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can decrypt traffic due to a weakness in the encryption protocol of IBM BigFix Remote Control.","url":"https://insights.sbomify.com/CVE-2015-4953/"}