{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-1000030 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2016-1000030 is a critical code injection vulnerability in Pidgin Pidgin, published on 5 Sep 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-2016-1000030 and fix it if it is affected.\n\nWhat it is: CVE-2016-1000030 is a critical code injection vulnerability in Pidgin Pidgin, published on 5 Sep 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-2016-1000030 in the wild and no public exploit code.\n\nAffected product: Pidgin Pidgin. 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-2016-1000030/ (Markdown: https://insights.sbomify.com/CVE-2016-1000030/index.md)","id":"CVE-2016-1000030","markdown":"https://insights.sbomify.com/CVE-2016-1000030/index.md","name":"CVE-2016-1000030","record":{"aliases":["DEBIAN-CVE-2016-1000030","GHSA-mxjf-9j2x-85mg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pidgin IM client","requires_auth":"none","summary":"Attackers can execute arbitrary code by sending a malicious X.509 certificate to Pidgin users due to improper return value checks.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pidgin","vendor":"pidgin"},{"product":"linux_enterprise_server","vendor":"suse"}],"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-295","name":"Improper Certificate Validation"}],"description":"Pidgin version \u003c2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutls_x509_crt_init() and gnutls_x509_crt_import() that can result in code execution. This attack appear to be exploitable via custom X.509 certificate from another client. This vulnerability appears to have been fixed in 2.11.0.","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":"Code injection in n/a","id":"CVE-2016-1000030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"pidgin:pidgin","products":["pidgin:pidgin","suse:linux_enterprise_server"],"type":"code_injection","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Improper Access Control in commons-fileupload","id":"CVE-2016-1000031"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2016-1000029"},"products":["n/a"],"published":"2018-09-05","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-6490","kev_date_added":null,"published":"2014-02-06"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2013-6486","kev_date_added":null,"published":"2014-02-06"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2011-3185","kev_date_added":null,"published":"2011-08-29"},{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2009-1376","kev_date_added":null,"published":"2009-05-26"},{"cvss_score":9,"headline":"Command injection in n/a","id":"CVE-2007-3841","kev_date_added":null,"published":"2007-07-17"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2013-6487","kev_date_added":null,"published":"2014-02-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-08-06","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by sending a malicious X.509 certificate to Pidgin users due to improper return value checks.","url":"https://insights.sbomify.com/CVE-2016-1000030/"}