{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17076 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17076 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17076 is a critical unsafe deserialization vulnerability in n/a, published on 8 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17076 and fix it if it is affected.\n\nWhat it is: CVE-2019-17076 is a critical unsafe deserialization vulnerability in n/a, published on 8 Jan 2020. 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-2019-17076 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-2019-17076/ (Markdown: https://insights.sbomify.com/CVE-2019-17076/index.md)","id":"CVE-2019-17076","markdown":"https://insights.sbomify.com/CVE-2019-17076/index.md","name":"CVE-2019-17076","record":{"aliases":["GHSA-mrxg-ghr4-x5rm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Jamf Pro server","requires_auth":"none","summary":"Untrusted JSON deserialization in Jamf Pro APIs allows attackers to execute code, cause denial of service, or delete files.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jamf","vendor":"jamf"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"An issue was discovered in Jamf Pro 9.x and 10.x before 10.15.1. Deserialization of untrusted data when parsing JSON in several APIs may cause Denial of Service (DoS), remote code execution (RCE), and/or deletion of files on the Jamf Pro server.","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":"Deserialization in n/a","id":"CVE-2019-17076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Deserialization in n/a","id":"CVE-2019-17080"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-17075"},"products":["n/a"],"published":"2020-01-08","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-31224","kev_date_added":null,"published":"2023-12-25"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2021-39303","kev_date_added":null,"published":"2021-11-12"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-40809","kev_date_added":null,"published":"2021-12-01"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2018-10465","kev_date_added":null,"published":"2020-01-07"},{"cvss_score":6.1,"headline":"Open redirect in n/a","id":"CVE-2021-35037","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-30125","kev_date_added":null,"published":"2021-04-02"}],"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":"Untrusted JSON deserialization in Jamf Pro APIs allows attackers to execute code, cause denial of service, or delete files.","url":"https://insights.sbomify.com/CVE-2019-17076/"}