Security readout for executives and security teams
Plain-English summary
This flaw can let unauthenticated network traffic exhaust memory on affected Juniper SRX firewalls. The result is a denial of service where all services stop functioning and manual restart is required. Exposure is configuration-dependent: APBR must be enabled without AppQoE SLA rules for those APBR rules.
Executive priority
Treat as high priority for SRX firewalls that protect critical traffic paths and use APBR. The business impact is service outage, not data theft, but recovery may require manual restart. Prioritize remediation based on configuration exposure and network criticality.
Technical view
CVE-2022-22205 is a CWE-401 memory leak in the AppQoE subsystem of the PFE on Juniper SRX Series running affected Junos OS releases. Specific sustained traffic in an APBR scenario can cause FPC memory exhaustion. CVSS 3.1 is 7.5: network, low complexity, no privileges, no user interaction, availability impact only.
Likely exposure
Likely exposure is limited to Juniper SRX Series devices running Junos OS 20.3 through 21.3 affected builds, with APBR configured and AppQoE SLA rules absent for those APBR rules. Junos OS before 20.3R1 is stated as not affected.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The vulnerability is remotely reachable and unauthenticated, but appears dependent on sustained specific traffic and a narrower APBR/AppQoE configuration state.
Researcher notes
Focus triage on the AppQoE/PFE/APBR interaction and FPC memory behavior. The public description identifies the vulnerable condition but does not provide exploit details. Avoid assuming exploit availability or broader Junos exposure beyond SRX Series and listed releases.
Mitigation direction
- Upgrade affected SRX devices to the fixed Junos OS release for their branch.
- Prioritize SRX firewalls using APBR without AppQoE SLA rules.
- Check Juniper JSA69709 for any supported interim mitigation or workaround.
- Prepare restart and failover procedures for exposed devices until remediation is complete.
Validation and detection
- Inventory SRX Series devices and record Junos OS release branches and patch levels.
- Check whether APBR is configured on each SRX device.
- Verify whether AppQoE SLA rules exist for configured APBR rules.
- Confirm upgraded devices run a fixed release listed in the advisory.
- Monitor FPC/PFE memory behavior on exposed devices before remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2022-22205 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (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:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://kb.juniper.net/JSA69709CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.