{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5836 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-5836 is a high-severity memory corruption vulnerability in n/a, published on 3 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-5836 and fix it if it is affected.\n\nWhat it is: CVE-2017-5836 is a high-severity memory corruption vulnerability in n/a, published on 3 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-5836 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-5836/ (Markdown: https://insights.sbomify.com/CVE-2017-5836/index.md)","id":"CVE-2017-5836","markdown":"https://insights.sbomify.com/CVE-2017-5836/index.md","name":"CVE-2017-5836","record":{"aliases":["AZL-36956","AZL-7269","DEBIAN-CVE-2017-5836","GHSA-978x-427c-qcqh","UBUNTU-CVE-2017-5836"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libplist library","requires_auth":"none","summary":"Attackers can cause a denial of service via a crash in libplist due to an invalid free triggered by improper handling of integer nodes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libplist","vendor":"libimobiledevice"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"The plist_free_data function in plist.c in libplist allows attackers to cause a denial of service (crash) via vectors involving an integer node that is treated as a PLIST_KEY and then triggers an invalid free.","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":"Memory corruption in n/a","id":"CVE-2017-5836","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-5837"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-5835"},"products":["n/a"],"published":"2017-03-03","related":[{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2017-5545","kev_date_added":null,"published":"2017-01-21"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2017-5209","kev_date_added":null,"published":"2017-01-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-5835","kev_date_added":null,"published":"2017-03-03"},{"cvss_score":5.5,"headline":"UIKit0 libplist XML xplist.c plist_from_xml xml external entity reference","id":"CVE-2015-10082","kev_date_added":null,"published":"2023-02-21"},{"cvss_score":5.5,"headline":"Integer overflow in n/a","id":"CVE-2017-7982","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2017-5834","kev_date_added":null,"published":"2017-03-03"}],"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":"Attackers can cause a denial of service via a crash in libplist due to an invalid free triggered by improper handling of integer nodes.","url":"https://insights.sbomify.com/CVE-2017-5836/"}