Security Resilience

CVE-2023-36850

Juniper Junos 19.1 … 22.4

Published
14 July 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0030 21th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-36850 is a medium-severity Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) vulnerability in Juniper Junos. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An Improper Validation of Specified Index, Position, or Offset in Input vulnerability in the Connectivity Fault Management(CFM) module of Juniper Networks Junos OS on MX Series(except MPC10, MPC11 and LC9600) allows an adjacent attacker on the local broadcast domain to…

more

cause a Denial of Service(DoS). Upon receiving a malformed CFM packet, the MPC crashes. Continued receipt of these packets causes a sustained denial of service. This issue can only be triggered when CFM hasn't been configured. This issue affects: Juniper Networks Junos OS All versions prior to 19.1R3-S10 on MX Series; 19.2 versions prior to 19.2R3-S7 on MX Series; 19.3 versions prior to 19.3R3-S8 on MX Series; 19.4 versions prior to 19.4R3-S12 on MX Series; 20.1 version 20.1R1 and later versions on MX Series; 20.2 versions prior to 20.2R3-S7 on MX Series; 20.3 version 20.3R1 and later versions on MX Series; 20.4 versions prior to 20.4R3-S7 on MX Series; 21.1 versions prior to 21.1R3-S5 on MX Series; 21.2 versions prior to 21.2R3-S4 on MX Series; 21.3 versions prior to 21.3R3-S4 on MX Series; 21.4 versions prior to 21.4R3-S3 on MX Series; 22.1 versions prior to 22.1R3-S2 on MX Series; 22.2 versions prior to 22.2R3 on MX Series; 22.3 versions prior to 22.3R2, 22.3R3 on MX Series; 22.4 versions prior to 22.4R2 on MX Series.

CWE(s)
CWE-1285

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
attack.mitre.org →
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
attack.mitre.org →
T1016 System Network Configuration Discovery Discovery
Adversaries may look for details about the network configuration and settings, such as IP and/or MAC addresses, of systems they access or through information discovery of remote systems.
attack.mitre.org →
T1020.001 Traffic Duplication Exfiltration
Adversaries may leverage traffic mirroring in order to automate data exfiltration over compromised infrastructure.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-30378Same product: Juniper Junos
CVE-2023-36848Same product: Juniper Junos
CVE-2023-36832Same product: Juniper Junos
CVE-2023-22413Same product: Juniper Junos
CVE-2023-22410Same product: Juniper Junos
CVE-2023-28974Same product: Juniper Junos
CVE-2023-28976Same product: Juniper Junos
CVE-2024-21587Same product: Juniper Junos
CVE-2023-22416Same product: Juniper Junos
CVE-2023-22394Same product: Juniper Junos

Affected Assets

juniper
junos
19.1, 19.2, 19.3, 19.4, 20.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.1.1
  • V2.2.1
  • V2.2.2
  • V5.3.3

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
blocks

Patching and replacement can remediate instances of the weakness after discovery.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require input validation, preventing this class of flaw at development time.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach index/offset validation defects, but leaves a bounded remainder (e.g. incomplete enforcement across all languages, outsourced code without full assurance, or post-release changes)

A.8.26 Application security requirements partial match
blocks

A.8.26 explicitly lists resilience against SQL injections plus input validation/integrity checks (items d, j) as application security requirements to identify/address via risk assessment; this reaches a minority slice of index/offset validation defects but leaves most instances (non-web, non-SQL, incomplete enforcement, second-order) unaddressed by the requirements-setting process itself.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security engineering principles including data validation/sanitization, distrust-external-input, security-by-design reviews against attack patterns, and hardening; this reaches a minority slice of CWE-1285 (index/offset validation in new designs) but leaves most instances (existing code, incomplete application of principles, or post-design defects) exploitable.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require validation of indices, positions, and offsets before use.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect missing or incorrect index validation during development and acceptance.

A.8.9 Configuration management partial match
removes

References