LiveActive security incident?Get immediate response
CVE Record

CVE-2021-0225: Junos OS Evolved: Stateless IP firewall filter does not work as expected

An Improper Check for Unusual or Exceptional Conditions in Juniper Networks Junos OS Evolved may cause the stateless firewall filter configuration which uses the action 'policer' in certain combinations with other options to not take effect. An administrator can use the following CLI command to see the failures with filter configuration: user@device> show log kfirewall-agent.log | match ERROR Jul 23 14:16:03 ERROR: filter not supported This issue affects Juniper Networks Junos OS Evolved: Versions 19.1R1-EVO and above prior to 20.3R1-S2-EVO, 20.3R2-EVO. This issue does not affect Juniper Networks Junos OS.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Juniper Junos OS Evolved firewall rules may silently fail when stateless filters use policer actions with certain option combinations. The business risk is that intended network traffic controls may not be enforced, weakening segmentation or rate-control assumptions.

Executive priority

Prioritize remediation where affected devices enforce perimeter, segmentation, tenant, or abuse-control policies. This is not rated critical, but failed network controls can create business exposure if teams assume filters are working.

Technical view

CVE-2021-0225 is an improper exceptional-condition handling issue in Junos OS Evolved. Affected stateless IP firewall filter configurations using 'policer' with certain other options may not take effect. Junos OS is explicitly not affected.

Likely exposure

Exposure is limited to Juniper Networks devices running Junos OS Evolved 19.1R1-EVO and later before 20.3R1-S2-EVO or 20.3R2-EVO, with affected stateless firewall filter configurations using policer actions.

Exploitation context

The source bundle does not report active exploitation, and this CVE is not listed as KEV. The practical risk is control failure rather than code execution: traffic handling may differ from the administrator's intended policy.

Researcher notes

Evidence is limited to the CVE record and Juniper advisory reference. The stated impact is low integrity with no confidentiality or availability impact in CVSS. Validate through configuration review and vendor log indicators, not exploit reproduction.

Mitigation direction

  • Upgrade affected Junos OS Evolved systems to 20.3R1-S2-EVO, 20.3R2-EVO, or later vendor-advised fixed releases.
  • Review Juniper advisory JSA11120 for platform-specific remediation guidance before maintenance.
  • Avoid unsupported policer filter combinations where feasible until upgraded and validated.
  • Treat dependent segmentation or rate-control policies as unreliable until enforcement is confirmed.

Validation and detection

  • Inventory Junos OS Evolved versions and confirm whether Junos OS, not Evolved, is excluded.
  • Identify stateless firewall filters using the policer action with additional options.
  • Check kfirewall-agent.log for 'ERROR: filter not supported' on affected devices.
  • Confirm intended filters are active after upgrade or configuration adjustment.
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-754: 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-0225 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
Medium
CVSS
5.8 (3.1)
Known Exploited
No
Published

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

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
5.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.8Medium
CVSS 3.1 vector shape for CVE-2021-0225Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 OS Evolved19.1R1-EVO, 20.3-EVOListed
Weakness

CWE details

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

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.