5.9

CVE-2021-0263: juniper networks junos os Data Processing Errors

CVSS: 5.9v3.1MediumModified
Published 22-04-2021Last modified 16-09-2024

Vulnerability summary

CVE-2021-0263 is a medium (CVSS 5.9) Data Processing Errors vulnerability in juniper networks junos os. EPSS estimates a 0.92% chance of exploitation in the next 30 days, higher than 59.5% of scored vulnerabilities.

Overall risk
24/100
0100
Low · default modelHow is this calculated?
CVSS score
5.9/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.92%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 22-04-2021
    PublishedVulnerability first disclosed.
  2. 16-09-2024
    Last modifiedVulnerability information updated.

Description

A Data Processing vulnerability in the Multi-Service process (multi-svcs) on the FPC of Juniper Networks Junos OS on the PTX Series routers may lead to the process becoming unresponsive, ultimately affecting traffic forwarding, allowing an attacker to cause a Denial of Service (DoS) condition . The Multi-Service Process running on the FPC is responsible for handling sampling-related operations when a J-Flow configuration is activated. This can occur during periods of heavy route churn, causing the Multi-Service Process to stop processing updates, without consuming any further updates from kernel. This back pressure towards the kernel affects further dynamic updates from other processes in the system, including RPD, causing a KRT-STUCK condition and traffic forwarding issues. An administrator can monitor the following command to check if there is the KRT queue is stuck: user@device > show krt state ... Number of async queue entries: 65007 <--- this value keep on increasing. The following logs/alarms will be observed when this condition exists: user@junos> show chassis alarms 2 alarms currently active Alarm time Class Description 2020-10-11 04:33:45 PDT Minor Potential slow peers are: MSP(FPC1-PIC0) MSP(FPC3-PIC0) MSP(FPC4-PIC0) Logs: Oct 11 04:33:44.672 2020 test /kernel: rts_peer_cp_recv_timeout : Bit set for msp8 as it is stuck Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: Error in parsing composite nexthop Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: composite nexthop parsing error Oct 11 04:43:05 2020 test /kernel: rt_pfe_veto: Possible slowest client is msp38. States processed - 65865741. States to be processed - 0 Oct 11 04:55:55 2020 test /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8311787520) Current delayed unref = (60000), Current unique delayed unref = (10896), Max delayed unref on this platform = (40000) Current delayed weight unref = (71426) Max delayed weight unref on this platform= (400000) curproc = rpd Oct 11 04:56:00 2020 test /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2 This issue only affects PTX Series devices. No other products or platforms are affected by this vulnerability. This issue affects Juniper Networks Junos OS on PTX Series: 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S8, 18.4R3-S7; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S2, 20.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 18.2R1.

CVSS metrics

3 scores · 2 sources · 2 versions

EPSS trend

Probability

0.92%

Chance of exploitation in the next 30 days

Percentile

60%

Versus all other CVEs

30-day change

0.00 pp

From 0.92% on 20-09-2026

20-09-202620-10-2026
EPSS score
0.92%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Juniper1 product
  • junos18.2 | 18.2:r1 | 18.2:r1-s2 | 18.2:r1-s3 | 18.2:r1-s4 | 18.2:r1-s5 | 18.2:r2 | 18.2:r2-s1 | 18.2:r2-s2 | 18.2:r2-s3 | 18.2:r2-s4 | 18.2:r2-s5 | 18.2:r2-s6 | 18.2:r2-s7 | 18.2:r3 | 18.2:r3-s1 | 18.2:r3-s2 | 18.2:r3-s3 | 18.2:r3-s4 | 18.2:r3-s5 | 18.2:r3-s6 | 18.3 | 18.3:r1 | 18.3:r1-s1 | 18.3:r1-s2 | 18.3:r1-s3 | 18.3:r1-s4 | 18.3:r1-s5 | 18.3:r1-s6 | 18.3:r2 | 18.3:r2-s1 | 18.3:r2-s2 | 18.3:r2-s3 | 18.3:r2-s4 | 18.3:r3 | 18.3:r3-s1 | 18.3:r3-s2 | 18.3:r3-s3 | 18.4 | 18.4:r1 | 18.4:r1-s1 | 18.4:r1-s2 | 18.4:r1-s3 | 18.4:r1-s4 | 18.4:r1-s5 | 18.4:r1-s6 | 18.4:r1-s7 | 18.4:r2 | 18.4:r2-s1 | 18.4:r2-s2 | 18.4:r2-s3 | 18.4:r2-s4 | 18.4:r2-s5 | 18.4:r2-s6 | 18.4:r2-s7 | 18.4:r3 | 18.4:r3-s1 | 18.4:r3-s2 | 18.4:r3-s3 | 18.4:r3-s4 | 18.4:r3-s5 | 18.4:r3-s6 | 19.1 | 19.1:r1 | 19.1:r1-s1 | 19.1:r1-s2 | 19.1:r1-s3 | 19.1:r1-s4 | 19.1:r1-s5 | 19.1:r2 | 19.1:r2-s1 | 19.1:r3 | 19.1:r3-s1 | 19.1:r3-s2 | 19.1:r3-s3 | 19.2 | 19.2:r1 | 19.2:r1-s1 | 19.2:r1-s2 | 19.2:r1-s3 | 19.2:r1-s4 | 19.2:r1-s5 | 19.2:r2 | 19.2:r2-s1 | 19.2:r3 | 19.3 | 19.3:r1 | 19.3:r1-s1 | 19.3:r2 | 19.3:r2-s1 | 19.3:r2-s2 | 19.3:r2-s3 | 19.3:r2-s4 | 19.3:r2-s5 | 19.3:r3 | 19.4:r1 | 19.4:r1-s1 | 19.4:r1-s2 | 19.4:r2 | 19.4:r2-s1 | 19.4:r2-s2 | 19.4:r2-s3 | 19.4:r3 | 20.1:r1 | 20.1:r1-s1 | 20.1:r1-s2 | 20.1:r1-s3 | 20.1:r1-s4 | 20.2:r1 | 20.2:r1-s1 | 20.2:r1-s2 | 20.2:r1-s3 | 20.3:r1 | 20.3:r1-s1
Juniper networks1 product
  • junos os≥ 18.2, < 18.2R3-S7 | ≥ 18.3, < 18.3R3-S4 | ≥ 18.4, < 18.4R2-S8, 18.4R3-S7 | ≥ 19.1, < 19.1R3-S4 | ≥ 19.2, < 19.2R3-S1 | ≥ 19.3, < 19.3R3-S1 | ≥ 19.4, < 19.4R2-S4, 19.4R3-S1 | ≥ 20.1, < 20.1R2 | ≥ 20.2, < 20.2R2 | ≥ 20.3, < 20.3R1-S2, 20.3R2

2 vendors · 2 products

References

2 links