# CVE-2022-22204: Denial of service in Junos OS > Unauthenticated attackers can cause a Denial of Service for SIP traffic on Juniper MX and SRX devices by sending specific packets that fill the call table. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 20 Jul 2022 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-gmwx-qv5p-38rc ## What is CVE-2022-22204? CVE-2022-22204 is a medium-severity denial of service vulnerability in Juniper Junos, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description An Improper Release of Memory Before Removing Last Reference vulnerability in the Session Initiation Protocol (SIP) Application Layer Gateway (ALG) of Juniper Networks Junos OS allows unauthenticated network-based attacker to cause a partial Denial of Service (DoS). On all MX and SRX platforms, if the SIP ALG is enabled, receipt of a specific SIP packet will create a stale SIP entry. Sustained receipt of such packets will cause the SIP call table to eventually fill up and cause a DoS for all SIP traffic. The SIP call usage can be monitored by "show security alg sip calls". To be affected the SIP ALG needs to be enabled, either implicitly / by default or by way of configuration. Please verify on SRX with: user@host> show security alg status | match sip SIP : Enabled Please verify on MX whether the following is configured: [ services ... rule (term ) from/match application/application-set ] where either a. name = junos-sip or an application or application-set refers to SIP: b. [ applications application application-protocol sip ] or c. [ applications application-set application junos-sip ] This issue affects Juniper Networks Junos OS on SRX Series and MX Series: 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R2-S2; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2; 21.4 versions prior to 21.4R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1. Juniper SIRT is not aware of any malicious exploitation of this vulnerability. Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime) ## Which versions are affected by CVE-2022-22204? It affects 1 product. Products: Juniper Junos. ## How do I fix CVE-2022-22204? No fix has been published for CVE-2022-22204 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-22204 being exploited? There is no known exploitation of CVE-2022-22204 in the wild and no public exploit code. ## Other vulnerabilities in Juniper Junos - [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild) - [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild) - [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild) - [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild) - [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-22204 and fix it if it is affected. What it is: CVE-2022-22204 is a medium-severity denial of service vulnerability in Juniper Junos, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-22204 in the wild and no public exploit code. Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-22204/ (Markdown: https://insights.sbomify.com/CVE-2022-22204/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22204 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22204 - OSV: https://osv.dev/vulnerability/CVE-2022-22204 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-22204/ Summaries are generated and may contain mistakes; the official description above is the record.