{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-0060 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-0060 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-0060 is a high-severity denial of service vulnerability in Juniper Junos, published on 9 Oct 2019. 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-0060 and fix it if it is affected.\n\nWhat it is: CVE-2019-0060 is a high-severity denial of service vulnerability in Juniper Junos, published on 9 Oct 2019. 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-0060 in the wild and no public exploit code.\n\nAffected product: Juniper Junos. 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-0060/ (Markdown: https://insights.sbomify.com/CVE-2019-0060/index.md)","id":"CVE-2019-0060","markdown":"https://insights.sbomify.com/CVE-2019-0060/index.md","name":"CVE-2019-0060","record":{"aliases":["GHSA-c5vr-66hv-6685"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Juniper SRX Gateway","requires_auth":"none","summary":"Attackers can cause a denial of service on Juniper SRX gateways by sending specific IP packets through configured IPSec tunnels.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos","vendor":"juniper"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"The flowd process, responsible for forwarding traffic in SRX Series services gateways, may crash and restart when processing specific transit IP packets through an IPSec tunnel. Continued processing of these packets may result in an extended Denial of Service (DoS) condition. This issue only occurs when IPSec tunnels are configured. Systems without IPSec tunnel configurations are not vulnerable to this issue. This issue affects Juniper Networks Junos OS: 15.1X49 versions prior to 15.1X49-D171, 15.1X49-D180 on SRX Series; 18.2 versions 18.2R2-S1 and later, prior to 18.2R3 on SRX Series; 18.4 versions prior to 18.4R2 on SRX Series.","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":"Junos OS: SRX Series: flowd process crash due to processing of specific transit IP packets","id":"CVE-2019-0060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos"],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Junos OS: Insecure management daemon (MGD) configuration may allow local privilege escalation","id":"CVE-2019-0061"},"packages":[],"prev":{"headline":"Denial of service in Junos OS","id":"CVE-2019-0059"},"products":["Junos OS"],"published":"2019-10-09","related":[{"cvss_score":9.8,"headline":"Juniper Junos OS EX Series and SRX Series PHP External Variable Modification","id":"CVE-2023-36845","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":8.8,"headline":"Juniper Junos OS Path Traversal","id":"CVE-2020-1631","kev_date_added":"2022-03-25","published":"2020-05-04"},{"cvss_score":6.7,"headline":"Juniper Junos OS Improper Isolation or Compartmentalization","id":"CVE-2025-21590","kev_date_added":"2025-03-13","published":"2025-03-12"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36851","kev_date_added":"2023-11-13","published":"2023-09-26"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series PHP External Variable Modification","id":"CVE-2023-36844","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36846","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series Missing Authentication for Critical Function","id":"CVE-2023-36847","kev_date_added":"2023-11-13","published":"2023-08-17"}],"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-09-16","vendors":["Juniper Networks"]},"summary":"Attackers can cause a denial of service on Juniper SRX gateways by sending specific IP packets through configured IPSec tunnels.","url":"https://insights.sbomify.com/CVE-2019-0060/"}