{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22198 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22198 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22198 is a high-severity vulnerability in Juniper Junos, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22198 and fix it if it is affected.\n\nWhat it is: CVE-2022-22198 is a high-severity vulnerability in Juniper Junos, published on 14 Apr 2022. 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-2022-22198 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-2022-22198/ (Markdown: https://insights.sbomify.com/CVE-2022-22198/index.md)","id":"CVE-2022-22198","markdown":"https://insights.sbomify.com/CVE-2022-22198/index.md","name":"CVE-2022-22198","record":{"aliases":["GHSA-xwh6-w3pq-2jj3"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Juniper Junos OS","requires_auth":"none","summary":"An unauthenticated attacker can cause a denial of service on Juniper MX and SRX devices by sending crafted SIP messages when the SIP ALG is enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"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-824","name":"Access of Uninitialized Pointer"}],"description":"An Access of Uninitialized Pointer vulnerability in the SIP ALG of Juniper Networks Junos OS allows an unauthenticated network-based attacker to cause a Denial of Service (DoS). Continued receipt of these specific packets will cause a sustained Denial of Service condition. On all MX and SRX platforms, if the SIP ALG is enabled, an MS-MPC or MS-MIC, or SPC will crash if it receives a SIP message with a specific contact header format. This issue affects Juniper Networks Junos OS on MX Series and SRX Series: 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect versions prior to 20.4R1.","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: MX MS-MPC or MS-MIC, or SRX SPC crashes if it receives a SIP message with a specific contact header format","id":"CVE-2022-22198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos"],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-22199"},"packages":[],"prev":{"headline":"Use after free in Junos OS","id":"CVE-2022-22197"},"products":["Junos OS"],"published":"2022-04-14","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-17","vendors":["Juniper Networks"]},"summary":"An unauthenticated attacker can cause a denial of service on Juniper MX and SRX devices by sending crafted SIP messages when the SIP ALG is enabled.","url":"https://insights.sbomify.com/CVE-2022-22198/"}