What is CVE-2023-4481?A high-severity flaw in Junos, explained.
CVE-2023-4481 is a high-severity flaw (CVSS 7.5) in Junos from Juniper, published on 1 September 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 18%. If you run an affected version, plan in the vendor’s fix.
Published 1 September 2023. Record last updated 15 October 2024. We keep this page's data up to date.
What is CVE-2023-4481? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS).
When certain specific crafted BGP UPDATE messages are received over an established BGP session, one BGP session may be torn down with an UPDATE message error, or the issue may propagate beyond the local system which will remain non-impacted, but may affect one or more remote systems. This issue is exploitable remotely as the crafted UPDATE message can propagate through unaffected systems and intermediate BGP speakers. Continuous receipt of the crafted BGP UPDATE messages will create a sustained Denial of Service (DoS) condition for impacted devices.
This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations. This issue requires a remote attacker to have at least one established BGP session. Improper Input Validation, Denial of Service vulnerability in Juniper Networks, Inc. Junos OS (BGP, rpd modules), Juniper Networks, Inc. Junos OS Evolved (BGP, rpd modules) allows Fuzzing.This issue affects
Junos OS:
* All versions before 20.4R3-S10, * from 21.1R1 through 21.*, * from 21.2 before 21.2R3-S5, * from 21.3 before 21.3R3-S5, * from 21.4 before 21.4R3-S7 (unaffected from 21.4R3-S5, affected from 21.4R3-S6) * from 22.1 before 22.1R3-S4, * from 22.2 before 22.2R3-S3, * from 22.3 before 22.3R3-S1, * from 22.4 before 22.4R3, * from 23.2 before 23.2R2.
Junos OS Evolved:
* All versions before 20.4R3-S10-EVO, * from 21.2-EVO before 21.2R3-S7-EVO, * from 21.3-EVO before 21.3R3-S5-EVO, * from 21.4-EVO before 21.4R3-S5-EVO, * from 22.1-EVO before 22.1R3-S4-EVO, * from 22.2-EVO before 22.2R3-S3-EVO, * from 22.3-EVO before 22.3R3-S1-EVO, * from 22.4-EVO before 22.4R3-EVO, * from 23.2-EVO before 23.2R2-EVO.
What kind of flaw is it?
- CWE-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2023-4481 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 18%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
CVE-2023-4481 scores 48. Action: Plan remediation.
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-4481 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-4481? 2 products.
The published record lists 2 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 - Operating system
Junos OS Evolved
by Juniper
Affected versionsbefore 20.420.420.4-r120.4-r1-s120.4-r1-s220.4-r220.4-r2-s120.4-r2-s220.4-r2-s320.4-r320.4-r3-s120.4-r3-s220.4-r3-s320.4-r3-s420.4-r3-s520.4-r3-s620.4-r3-s720.4-r3-s820.4-r3-s921.221.2-r121.2-r1-s121.2-r1-s221.2-r221.2-r2-s121.2-r2-s221.2-r321.2-r3-s121.2-r3-s221.2-r3-s321.2-r3-s421.2-r3-s521.2-r3-s621.321.3-r121.3-r1-s121.3-r221.3-r2-s121.3-r2-s221.3-r3
How do I fix CVE-2023-4481? 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 advisories and patch notes 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.
Does CVE-2023-4481 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
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, ...
- 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-4481 is a high-severity flaw in Junos from Juniper, published on 1 September 2023. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2023-4481 is 48 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
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 18%. 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 90 more. The record lists 2 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.