LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22204: Junos OS: MX Series and SRX Series: When receiving a specific SIP packets stale call table entries are created which eventually leads to a DoS for all SIP traffic

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 <rule-name> (term <term-name>) from/match application/application-set <name> ] where either a. name = junos-sip or an application or application-set refers to SIP: b. [ applications application <name> application-protocol sip ] or c. [ applications application-set <name> 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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Juniper MX and SRX devices running affected Junos OS versions can lose SIP traffic handling if SIP ALG is enabled. Specific SIP packets can leave stale call entries behind until the SIP call table fills, causing a partial denial of service. The issue does not require authentication, but the documented impact is limited to SIP availability.

Executive priority

Treat this as a moderate availability risk for sites depending on SIP voice or session services through Juniper SRX or MX devices. Prioritize remediation where SIP ALG is enabled on exposed or high-dependence network paths.

Technical view

CVE-2022-22204 is a CWE-401 memory/reference cleanup flaw in the Junos OS SIP ALG. A network attacker can trigger stale SIP call table entries through specific SIP packets. Affected branches are 20.4, 21.1, 21.2, 21.3, and 21.4 before Juniper’s fixed releases. Junos versions before 20.4R1 are not affected.

Likely exposure

Exposure is most likely where Juniper SRX or MX platforms run affected Junos OS and SIP ALG is enabled by default, implicitly, or through service/application configuration. Environments not using SIP ALG are outside the described affected condition.

Exploitation context

The source states Juniper SIRT was not aware of malicious exploitation. The CVE is not listed as KEV in the supplied bundle. The attack is unauthenticated and network-based, but requires sustained specific SIP traffic to fill the call table.

Researcher notes

Key constraints are SIP ALG enablement and affected Junos branch. The public description names detection points for SRX and MX configuration, but does not provide packet details. Avoid assuming broader protocol or device impact beyond MX, SRX, Junos OS, and SIP ALG.

Mitigation direction

  • Upgrade to Juniper fixed releases for the deployed Junos OS branch.
  • Review Juniper JSA69708 before changing SIP ALG or production voice traffic behavior.
  • Disable SIP ALG where it is not required for business operations.
  • Monitor SIP call table usage for abnormal growth until upgrades are complete.

Validation and detection

  • Check SRX SIP ALG status with the vendor-documented status check.
  • Review MX services rules for SIP applications or application sets.
  • Inventory MX and SRX devices running Junos OS 20.4 through 21.4.
  • Monitor SIP call usage for stale entries or sustained table growth.
  • Confirm upgraded devices meet or exceed Juniper’s fixed release levels.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-22204 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-22204Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OSunspecified, 20.4, 21.1, 21.2, 21.3, 21.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.