LiveActive security incident?Get immediate response
CVE Record

CVE-2019-0036: Junos OS: Firewall filter terms named "internal-1" and "internal-2" being ignored

When configuring a stateless firewall filter in Junos OS, terms named using the format "internal-n" (e.g. "internal-1", "internal-2", etc.) are silently ignored. No warning is issued during configuration, and the config is committed without error, but the filter criteria will match all packets leading to unexpected results. Affected releases are Juniper Networks Junos OS: All versions prior to and including 12.3; 14.1X53 versions prior to 14.1X53-D130, 14.1X53-D49; 15.1 versions prior to 15.1F6-S12, 15.1R7-S4; 15.1X49 versions prior to 15.1X49-D161, 15.1X49-D170; 15.1X53 versions prior to 15.1X53-D236, 15.1X53-D496, 15.1X53-D69; 16.1 versions prior to 16.1R7-S4, 16.1R7-S5; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R1-S8, 17.2R3-S1; 17.3 versions prior to 17.3R3-S4; 17.4 versions prior to 17.4R1-S7, 17.4R2-S3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S4; 18.2 versions prior to 18.2R1-S5, 18.2R2-S1; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S3; 18.4 versions prior to 18.4R1-S1, 18.4R1-S2.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some Junos OS firewall rules can be silently ignored if their term names follow the pattern internal-1, internal-2, and similar. A device may accept the configuration without warning while enforcing broader traffic matching than intended. This can weaken network access controls where affected filters protect sensitive paths.

Executive priority

Treat as high priority for Juniper estates that rely on Junos firewall filters for network control. The issue may silently undermine intended restrictions without configuration errors, making audit and upgrade planning important even without evidence of active exploitation.

Technical view

CVE-2019-0036 is a Junos OS stateless firewall filter handling flaw. Terms named in the internal-n format are ignored at commit time without error, causing filter criteria to match all packets and creating unexpected access-control behavior. The issue is mapped to CWE-284 and has CVSS 3.0 score 7.2.

Likely exposure

Exposure is most likely in Juniper Junos OS environments running the listed affected trains and using stateless firewall filters with term names like internal-1 or internal-2. Business impact depends on where those filters are applied and whether they enforce segmentation, permit/deny policy, or control-plane protection.

Exploitation context

The provided bundle does not show CISA KEV listing or cited active exploitation. The risk is primarily misenforcement of intended firewall policy. A remote unauthenticated attacker may benefit if traffic reaches an interface where an affected filter is relied on for restriction.

Researcher notes

The source bundle identifies Junos OS releases through 18.4-era trains and fixed train-specific versions. Evidence is limited to the CVE record and Juniper advisory reference; no exploit details, public exploitation evidence, or independent workaround validation are included in the bundle.

Mitigation direction

  • Upgrade affected Junos OS trains to the vendor-listed fixed releases or later.
  • Review Juniper JSA10925 for train-specific remediation and any current vendor guidance.
  • Prioritize devices where stateless filters enforce segmentation or control-plane access.
  • Avoid deploying new firewall terms using the internal-n naming pattern.

Validation and detection

  • Inventory Junos OS versions against the affected and fixed release list.
  • Review stateless firewall filter configurations for term names matching internal-n.
  • Confirm affected filters are applied to interfaces or paths with security impact.
  • After remediation, verify intended packet matching behavior in a controlled change window.
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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2019-0036 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.2 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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
7.2CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.2High
CVSS 3.0 vector shape for CVE-2019-0036Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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 OS12.1X46, 12.3X48, 12.3, 14.1X53, 15.1, 15.1X49, 15.1X53, 16.1, 16.2, 17.1, 17.2, 17.3, 17.4, 18.1, 18.2, 18.2X75, 18.3, 18.4Listed
Weakness

CWE details

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

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.