What is CVE-2023-22392?A medium-severity flaw in Junos, explained.
CVE-2023-22392 is a medium-severity flaw (CVSS 6.5) in Junos from Juniper, published on 12 October 2023. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.3%. If you run an affected version, plan in the vendor’s fix.
Published 12 October 2023. Record last updated 21 February 2024. We keep this page's data up to date.
What is CVE-2023-22392? In plain terms.
An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
A Missing Release of Memory after Effective Lifetime vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).
PTX3000, PTX5000, QFX10000, PTX1000, PTX10002, and PTX10004, PTX10008 and PTX10016 with LC110x FPCs do not support certain flow-routes. Once a flow-route is received over an established BGP session and an attempt is made to install the resulting filter into the PFE, FPC heap memory is leaked. The FPC heap memory can be monitored using the CLI command "show chassis fpc".
The following syslog messages can be observed if the respective filter derived from a flow-route cannot be installed.
expr_dfw_sfm_range_add:661 SFM packet-length Unable to get a sfm entry for updating the hw expr_dfw_hw_sfm_add:750 Unable to add the filter secondarymatch to the hardware expr_dfw_base_hw_add:52 Failed to add h/w sfm data. expr_dfw_base_hw_create:114 Failed to add h/w data. expr_dfw_base_pfe_inst_create:241 Failed to create base inst for sfilter 0 on PFE 0 for __flowspec_default_inet__ expr_dfw_flt_inst_change:1368 Failed to create __flowspec_default_inet__ on PFE 0 expr_dfw_hw_pgm_fnum:465 dfw_pfe_inst_old not found for pfe_index 0! expr_dfw_bp_pgm_flt_num:548 Failed to pgm bind-point in hw: generic failure expr_dfw_bp_topo_handler:1102 Failed to program fnum. expr_dfw_entry_process_change:679 Failed to change instance for filter __flowspec_default_inet__. This issue affects Juniper Networks Junos OS:
on PTX1000, PTX10002, and PTX10004, PTX10008 and PTX10016 with LC110x FPCs:
* All versions prior to 20.4R3-S5; * 21.1 versions prior to 21.1R3-S4; * 21.2 versions prior to 21.2R3-S2; * 21.3 versions prior to 21.3R3; * 21.4 versions prior to 21.4R2-S2, 21.4R3; * 22.1 versions prior to 22.1R1-S2, 22.1R2.
on PTX3000, PTX5000, QFX10000:
* All versions prior to 20.4R3-S8; * 21.1 version 21.1R1 and later versions; * 21.2 versions prior to 21.2R3-S6; * 21.3 versions prior to 21.3R3-S5; * 21.4 versions prior to 21.4R3-S4; * 22.1 versions prior to 22.1R3-S3 * 22.2 versions prior to 22.2R3-S1 * 22.3 versions prior to 22.3R2-S2, 22.3R3 * 22.4 versions prior to 22.4R2.
What kind of flaw is it?
- CWE-401Missing Release of Memory after Effective Lifetime
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2023-22392 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2023-22392 scores 27. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2023-22392 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2023-22392? 11 products.
The published record lists 11 products from 1 vendor. Versions are shown as published: "before 20.4" means every version up to, but not including, 20.4. If you run one of these, check your version, then go to the fix below.
- Operating system
Junos
by Juniper
Affected versionsbefore 20.420.420.4-r120.4-r1-s120.4-r220.4-r2-s120.4-r2-s220.4-r320.4-r3-s120.4-r3-s220.4-r3-s320.4-r3-s420.4-r3-s520.4-r3-s6 - Hardware
Ptx1000
by Juniper
Affected versionsversion not specified - Hardware
Ptx1000-72q
by Juniper
Affected versionsversion not specified - Hardware
Ptx10002
by Juniper
Affected versionsversion not specified - Hardware
Ptx10002-60c
by Juniper
Affected versionsversion not specified - Hardware
Ptx10004
by Juniper
Affected versionsversion not specified - Hardware
Ptx10008
by Juniper
Affected versionsversion not specified - Hardware
Ptx10016
by Juniper
Affected versionsversion not specified - Hardware
Ptx3000
by Juniper
Affected versionsversion not specified
How do I fix CVE-2023-22392? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
1 linkDoes CVE-2023-22392 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A Missing Release of Memory after Effective Lifetime vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an adjacent, una...
- Matched to
- Junos on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2023-22392 is a medium-severity flaw in Junos from Juniper, published on 12 October 2023. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2023-22392 is 27 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.
For Junos from Juniper: before 20.4, 20.4, 20.4-r1, 20.4-r1-s1, 20.4-r2, 20.4-r2-s1 and 81 more. The record lists 11 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.