LiveActive security incident?Get immediate response
CVE Record

CVE-2021-31354: Junos OS and Junos OS Evolved: A vulnerability in the Juniper Agile License Client may allow an attacker to perform Remote Code Execution (RCE)

An Out Of Bounds (OOB) access vulnerability in the handling of responses by a Juniper Agile License (JAL) Client in Juniper Networks Junos OS and Junos OS Evolved, configured in Network Mode (to use Juniper Agile License Manager) may allow an attacker to cause a partial Denial of Service (DoS), or lead to remote code execution (RCE). The vulnerability exists in the packet parsing logic on the client that processes the response from the server using a custom protocol. An attacker with control of a JAL License Manager, or with access to the local broadcast domain, may be able to spoof a new JAL License Manager and/or craft a response to the Junos OS License Client, leading to exploitation of this vulnerability. This issue only affects Junos systems configured in Network Mode. Systems that are configured in Standalone Mode (the default mode of operation for all systems) are not vulnerable to this issue. This issue affects: Juniper Networks Junos OS: 19.2 versions prior to 19.2R3-S3; 19.3 versions prior to 19.3R3-S3; 20.1 versions prior to 20.1R2-S2, 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. Juniper Networks Junos OS Evolved: version 20.1R1-EVO and later versions, prior to 21.2R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 19.2R1.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Juniper devices only when Junos is configured to use Juniper Agile License Manager in Network Mode. A nearby attacker, or one controlling the license manager, could crash part of the service or potentially run code. Standalone Mode, the default, is not vulnerable.

Executive priority

Prioritize remediation for Juniper routing or switching infrastructure using centralized agile licensing. The business risk is highest where attackers could access the same local network segment as the license client or influence the license manager.

Technical view

CVE-2021-31354 is an out-of-bounds access issue in JAL Client response parsing for a custom protocol. Exploitation requires Network Mode and either control of JAL License Manager or local broadcast-domain access to spoof or craft responses. Impact includes partial DoS or possible RCE.

Likely exposure

Exposure is limited to Junos OS 19.2 through affected 21.1 trains and Junos OS Evolved before 21.2R2-EVO when JAL Network Mode is enabled. Default Standalone Mode systems are not exposed per the source bundle.

Exploitation context

The CVSS vector is adjacent network, high complexity, no privileges, and no user interaction. The bundle does not cite CISA KEV listing or confirmed active exploitation, so active exploitation should not be assumed.

Researcher notes

The root issue maps to CWE-125 and sits in client-side response parsing. The important constraint is configuration-dependent reachability: vulnerable code exists only in Network Mode. Evidence is insufficient to claim internet-scale exploitation or public exploit availability.

Mitigation direction

  • Identify Junos systems using JAL Network Mode.
  • Upgrade affected Junos OS trains to the fixed release or later.
  • Upgrade Junos OS Evolved to 21.2R2-EVO or later.
  • Use Standalone Mode where Network Mode is not required.
  • Check Juniper JSA11219 for current vendor guidance.

Validation and detection

  • Confirm whether each device uses JAL Network Mode or default Standalone Mode.
  • Inventory Junos OS and Junos OS Evolved release trains.
  • Compare versions against the fixed releases listed by Juniper.
  • Review license-manager network adjacency and broadcast-domain exposure.
  • Monitor affected devices for partial DoS symptoms.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-31354 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L1.65.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2021-31354Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OSunspecified, 19.2, 19.3, 20.1, 20.2, 20.3, 20.4, 21.1Listed
Juniper NetworksJunos OS Evolved20.1R1-EVO, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.