LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0246: Junos OS: SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2/SPC3: In a multi-tenant environment, a tenant host administrator may be able to jailbreak out of their network impacting other tenant networks or gather information from other networks.

On SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2/SPC3, devices using tenant services on Juniper Networks Junos OS, due to incorrect default permissions assigned to tenant system administrators a tenant system administrator may inadvertently send their network traffic to one or more tenants while concurrently modifying the overall device system traffic management, affecting all tenants and the service provider. Further, a tenant may inadvertently receive traffic from another tenant. This issue affects: Juniper Networks Junos OS 18.3 version 18.3R1 and later versions on SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2; 18.3 versions prior to 18.3R3 on SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2; 18.4 versions prior to 18.4R2 on SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2/SPC3; 19.1 versions prior to 19.1R2 on SRX1500, SRX4100, SRX4200, SRX4600, SRX5000 Series with SPC2/SPC3. This issue does not affect: Juniper Networks Junos OS versions prior to 18.3R1.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some Juniper SRX firewalls running affected Junos OS tenant services may let a tenant administrator affect traffic handling beyond their own tenant. In multi-tenant deployments, this can expose one tenant’s traffic to another tenant or disrupt shared device traffic management.

Executive priority

Prioritize for managed security or service-provider environments where multiple customers share SRX tenant services. The business risk is tenant isolation failure, not broad internet compromise.

Technical view

CVE-2021-0246 is an incorrect default permissions issue in Junos OS tenant services on specified SRX platforms with SPC2 or SPC3. A high-privileged local tenant system administrator may alter device-wide traffic management or cause traffic leakage across tenants. CVSS is 7.3 with changed scope.

Likely exposure

Exposure appears limited to multi-tenant Juniper SRX1500, SRX4100, SRX4200, SRX4600, and SRX5000 Series deployments using tenant services on affected Junos OS releases and SPC2/SPC3 combinations.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The attack requires local access and high privileges as a tenant system administrator, but impact crosses tenant boundaries and can affect the service provider.

Researcher notes

Evidence supports a permission design flaw with local, high-privilege preconditions and cross-tenant impact. The bundle names affected release ranges but does not include exploit details, proof of active exploitation, or full vendor workaround text.

Mitigation direction

  • Inventory SRX tenant-service deployments and identify SPC2/SPC3 hardware.
  • Compare Junos OS releases against Juniper advisory JSA11139.
  • Upgrade or remediate according to Juniper’s vendor guidance.
  • Restrict tenant administrator access to trusted users until remediation is complete.
  • Review tenant isolation assumptions for affected shared-firewall services.

Validation and detection

  • Confirm whether tenant services are enabled on listed SRX platforms.
  • Record Junos OS version and hardware module type for each device.
  • Check for affected 18.3, 18.4, and 19.1 release levels.
  • Review configuration permissions granted to tenant system administrators.
  • Look for unexpected tenant-to-tenant traffic handling or routing anomalies.
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-276: 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
cve · low confidence lookup

CVE-2021-0246 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/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.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L1.55.3Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/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, 18.4, 19.1Listed
Juniper NetworksJunos OS18.3R1Listed
Weakness

CWE details

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.