{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-9704 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2019-9704 is a medium-severity vulnerability in Debian Debian Linux, published on 12 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9704 and fix it if it is affected.\n\nWhat it is: CVE-2019-9704 is a medium-severity vulnerability in Debian Debian Linux, published on 12 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-9704 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-9704/ (Markdown: https://insights.sbomify.com/CVE-2019-9704/index.md)","id":"CVE-2019-9704","markdown":"https://insights.sbomify.com/CVE-2019-9704/index.md","name":"CVE-2019-9704","record":{"aliases":["DEBIAN-CVE-2019-9704","GHSA-34r4-h4c9-vmrj","UBUNTU-CVE-2019-9704","openSUSE-SU-2024:10701-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vixie Cron","requires_auth":"low_privilege","summary":"Local users can crash the Vixie Cron daemon by submitting a large crontab file due to unchecked memory allocation failures.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cron","vendor":"cron_project"},{"product":"debian_linux","vendor":"debian"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"},{"id":"CWE-252","name":"Unchecked Return Value"}],"description":"Vixie Cron before the 3.0pl1-133 Debian package allows local users to cause a denial of service (daemon crash) via a large crontab file because the calloc return value is not checked.","ecosystems":["openSUSE:Tumbleweed"],"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-2019-9704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","fedoraproject:fedora"],"type":"null_dereference","year":"2019"},"n_packages":1,"n_references":5,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-9705"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.5.7-86.1"],"introduced":["0"],"last_affected":[],"package":"cronie","purl":"pkg:rpm/opensuse/cronie\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10701-1"}],"prev":{"headline":"Symantec Endpoint Encryption, prior to SEE 11.3.0, may be susceptible to a privilege escalation vulnerability, which is a type of issue that","id":"CVE-2019-9703"},"products":["n/a"],"published":"2019-03-12","related":[{"cvss_score":6.7,"headline":"Privilege escalation in n/a","id":"CVE-2017-9525","kev_date_added":null,"published":"2017-06-09"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2019-9705","kev_date_added":null,"published":"2019-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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-04","vendors":["n/a"]},"summary":"Local users can crash the Vixie Cron daemon by submitting a large crontab file due to unchecked memory allocation failures.","url":"https://insights.sbomify.com/CVE-2019-9704/"}