Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
Vulnerability Details :

CVE-2023-22410

Summary
Assigner-juniper
Assigner Org ID-8cbe9d5a-a066-4c94-8978-4b15efeae968
Published At-12 Jan, 2023 | 00:00
Updated At-07 Apr, 2025 | 15:32
Rejected At-
Credits

Junos OS: MX Series with MPC10/MPC11: When Suspicious Control Flow Detection (scfd) is enabled and an attacker is sending specific traffic, this causes a memory leak.

A Missing Release of Memory after Effective Lifetime vulnerability in the Juniper Networks Junos OS on MX Series platforms with MPC10/MPC11 line cards, allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). Devices are only vulnerable when the Suspicious Control Flow Detection (scfd) feature is enabled. Upon enabling this specific feature, an attacker sending specific traffic is causing memory to be allocated dynamically and it is not freed. Memory is not freed even after deactivating this feature. Sustained processing of such traffic will eventually lead to an out of memory condition that prevents all services from continuing to function, and requires a manual restart to recover. The FPC memory usage can be monitored using the CLI command "show chassis fpc". On running the above command, the memory of AftDdosScfdFlow can be observed to detect the memory leak. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 20.2R3-S5; 20.3 version 20.3R1 and later versions.

Vendors
-
Not available
Products
-
Metrics (CVSS)
VersionBase scoreBase severityVector
Weaknesses
Attack Patterns
Solution/Workaround
References
HyperlinkResource Type
EPSS History
Score
Latest Score
-
N/A
No data available for selected date range
Percentile
Latest Percentile
-
N/A
No data available for selected date range
Stakeholder-Specific Vulnerability Categorization (SSVC)
▼Common Vulnerabilities and Exposures (CVE)
cve.org
Assigner:juniper
Assigner Org ID:8cbe9d5a-a066-4c94-8978-4b15efeae968
Published At:12 Jan, 2023 | 00:00
Updated At:07 Apr, 2025 | 15:32
Rejected At:
▼CVE Numbering Authority (CNA)
Junos OS: MX Series with MPC10/MPC11: When Suspicious Control Flow Detection (scfd) is enabled and an attacker is sending specific traffic, this causes a memory leak.

A Missing Release of Memory after Effective Lifetime vulnerability in the Juniper Networks Junos OS on MX Series platforms with MPC10/MPC11 line cards, allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). Devices are only vulnerable when the Suspicious Control Flow Detection (scfd) feature is enabled. Upon enabling this specific feature, an attacker sending specific traffic is causing memory to be allocated dynamically and it is not freed. Memory is not freed even after deactivating this feature. Sustained processing of such traffic will eventually lead to an out of memory condition that prevents all services from continuing to function, and requires a manual restart to recover. The FPC memory usage can be monitored using the CLI command "show chassis fpc". On running the above command, the memory of AftDdosScfdFlow can be observed to detect the memory leak. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 20.2R3-S5; 20.3 version 20.3R1 and later versions.

Affected Products
Vendor
Juniper Networks, Inc.Juniper Networks
Product
Junos OS
Platforms
  • MX Series
Versions
Affected
  • From unspecified before 20.2R3-S5 (custom)
  • From 20.3R1 before 20.3* (custom)
Problem Types
TypeCWE IDDescription
CWECWE-401CWE-401 Missing Release of Memory after Effective Lifetime
textN/ADenial of Service (DoS)
Type: CWE
CWE ID: CWE-401
Description: CWE-401 Missing Release of Memory after Effective Lifetime
Type: text
CWE ID: N/A
Description: Denial of Service (DoS)
Metrics
VersionBase scoreBase severityVector
3.17.5HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Version: 3.1
Base score: 7.5
Base severity: HIGH
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Metrics Other Info
Impacts
CAPEC IDDescription
Solutions

The following software releases have been updated to resolve this specific issue: 20.2R3-S5, 20.4R1, and all subsequent releases.

Configurations

This issue only affects systems with scfd enabled. An minimal scfd configuration is shown below: [system ddos-protection global flow-detection]

Workarounds

There are no known workarounds for this issue.

Exploits

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

Credits

Timeline
EventDate
Replaced By

Rejected Reason

References
HyperlinkResource
https://kb.juniper.net/JSA70206
N/A
Hyperlink: https://kb.juniper.net/JSA70206
Resource: N/A
▼Authorized Data Publishers (ADP)
1. CVE Program Container
Affected Products
Metrics
VersionBase scoreBase severityVector
Metrics Other Info
Impacts
CAPEC IDDescription
Solutions

Configurations

Workarounds

Exploits

Credits

Timeline
EventDate
Replaced By

Rejected Reason

References
HyperlinkResource
https://kb.juniper.net/JSA70206
x_transferred
Hyperlink: https://kb.juniper.net/JSA70206
Resource:
x_transferred
2. CISA ADP Vulnrichment
Affected Products
Metrics
VersionBase scoreBase severityVector
Metrics Other Info
Impacts
CAPEC IDDescription
Solutions

Configurations

Workarounds

Exploits

Credits

Timeline
EventDate
Replaced By

Rejected Reason

References
HyperlinkResource
Information is not available yet
▼National Vulnerability Database (NVD)
nvd.nist.gov
Source:sirt@juniper.net
Published At:13 Jan, 2023 | 00:15
Updated At:20 Jan, 2023 | 07:58

A Missing Release of Memory after Effective Lifetime vulnerability in the Juniper Networks Junos OS on MX Series platforms with MPC10/MPC11 line cards, allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). Devices are only vulnerable when the Suspicious Control Flow Detection (scfd) feature is enabled. Upon enabling this specific feature, an attacker sending specific traffic is causing memory to be allocated dynamically and it is not freed. Memory is not freed even after deactivating this feature. Sustained processing of such traffic will eventually lead to an out of memory condition that prevents all services from continuing to function, and requires a manual restart to recover. The FPC memory usage can be monitored using the CLI command "show chassis fpc". On running the above command, the memory of AftDdosScfdFlow can be observed to detect the memory leak. This issue affects Juniper Networks Junos OS on MX Series: All versions prior to 20.2R3-S5; 20.3 version 20.3R1 and later versions.

CISA Catalog
Date AddedDue DateVulnerability NameRequired Action
N/A
Date Added: N/A
Due Date: N/A
Vulnerability Name: N/A
Required Action: N/A
Metrics
TypeVersionBase scoreBase severityVector
Primary3.16.5MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Secondary3.17.5HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Type: Primary
Version: 3.1
Base score: 6.5
Base severity: MEDIUM
Vector:
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Type: Secondary
Version: 3.1
Base score: 7.5
Base severity: HIGH
Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CPE Matches

Juniper Networks, Inc.
juniper
>>junos>>Versions before 20.2(exclusive)
cpe:2.3:o:juniper:junos:*:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:-:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r1-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r1-s2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r1-s3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r2-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r2-s2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r2-s3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r3-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r3-s2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r3-s3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.2
cpe:2.3:o:juniper:junos:20.2:r3-s4:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:-:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r1-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r1-s2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r2-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s1:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s2:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s3:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s4:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s5:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>junos>>20.3
cpe:2.3:o:juniper:junos:20.3:r3-s6:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx10>>-
cpe:2.3:h:juniper:mx10:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx10000>>-
cpe:2.3:h:juniper:mx10000:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx10003>>-
cpe:2.3:h:juniper:mx10003:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx10008>>-
cpe:2.3:h:juniper:mx10008:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx10016>>-
cpe:2.3:h:juniper:mx10016:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx104>>-
cpe:2.3:h:juniper:mx104:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx150>>-
cpe:2.3:h:juniper:mx150:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx2008>>-
cpe:2.3:h:juniper:mx2008:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx2010>>-
cpe:2.3:h:juniper:mx2010:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx2020>>-
cpe:2.3:h:juniper:mx2020:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx204>>-
cpe:2.3:h:juniper:mx204:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx240>>-
cpe:2.3:h:juniper:mx240:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx40>>-
cpe:2.3:h:juniper:mx40:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx480>>-
cpe:2.3:h:juniper:mx480:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx5>>-
cpe:2.3:h:juniper:mx5:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx80>>-
cpe:2.3:h:juniper:mx80:-:*:*:*:*:*:*:*
Juniper Networks, Inc.
juniper
>>mx960>>-
cpe:2.3:h:juniper:mx960:-:*:*:*:*:*:*:*
Weaknesses
CWE IDTypeSource
CWE-401Primarynvd@nist.gov
CWE-401Secondarysirt@juniper.net
CWE ID: CWE-401
Type: Primary
Source: nvd@nist.gov
CWE ID: CWE-401
Type: Secondary
Source: sirt@juniper.net
Evaluator Description

Evaluator Impact

Evaluator Solution

Vendor Statements

References
HyperlinkSourceResource
https://kb.juniper.net/JSA70206sirt@juniper.net
Exploit
Vendor Advisory
Hyperlink: https://kb.juniper.net/JSA70206
Source: sirt@juniper.net
Resource:
Exploit
Vendor Advisory

Change History

0
Information is not available yet

Similar CVEs

0Records found

Details not found