{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-5668 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-5668 is a critical vulnerability in n/a, published on 14 Mar 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-2017-5668 and fix it if it is affected.\n\nWhat it is: CVE-2017-5668 is a critical vulnerability in n/a, published on 14 Mar 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-2017-5668 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-2017-5668/ (Markdown: https://insights.sbomify.com/CVE-2017-5668/index.md)","id":"CVE-2017-5668","markdown":"https://insights.sbomify.com/CVE-2017-5668/index.md","name":"CVE-2017-5668","record":{"aliases":["DEBIAN-CVE-2017-5668","GHSA-x9m7-9m6q-c6hr","UBUNTU-CVE-2017-5668"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitlbee IM gateway","requires_auth":"none","summary":"Remote attackers can cause a crash or potentially execute code via a file transfer request to an unknown contact in Bitlbee.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitlbee","vendor":"bitlbee"},{"product":"bitlbee-libpurple","vendor":"bitlbee"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"bitlbee-libpurple before 3.5.1 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) and possibly execute arbitrary code via a file transfer request for a contact that is not in the contact list.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-10189.","ecosystems":[],"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":"Null dereference in n/a","id":"CVE-2017-5668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2017"},"n_packages":0,"n_references":5,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-5669"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-5667"},"products":["n/a"],"published":"2017-03-14","related":[{"cvss_score":9.8,"headline":"Privilege escalation in Bitlbee","id":"CVE-2012-1187","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2016-10188","kev_date_added":null,"published":"2017-03-14"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2016-10189","kev_date_added":null,"published":"2017-03-14"},{"cvss_score":7.5,"headline":"Unspecified vulnerability in BitlBee before 1.2.2 allows remote attackers to \"recreate\" and \"hijack\" existing accounts via unspecified vectors.","id":"CVE-2008-3920","kev_date_added":null,"published":"2008-09-04"},{"cvss_score":5,"headline":"Multiple unspecified vulnerabilities in BitlBee before 1.2.3 allow remote attackers to \"overwrite\" and \"hijack\" existing accounts via unknow","id":"CVE-2008-3969","kev_date_added":null,"published":"2008-09-10"}],"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":"Remote attackers can cause a crash or potentially execute code via a file transfer request to an unknown contact in Bitlbee.","url":"https://insights.sbomify.com/CVE-2017-5668/"}