Vulnerability-Lookup

GHSA-M7P5-CQG5-94P6

Vulnerability from github – Published: 2026-04-10 00:30 – Updated: 2026-04-10 00:30

Details

When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.

This issue affects Junos OS on EX Series and QFX Series: * 23.4 version 23.4R2-S6, * 24.2 version 24.2R2-S3.

No other Junos OS versions are affected.

Severity ?

5.8 (Medium)


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

6.9 (Medium)


                  
                    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/AU:Y/R:U/RE:M

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-33773"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-04-09T22:16:25Z",
    "severity": "MODERATE"
  },
  "details": "An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks.\n\nWhen the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.\n\nThis issue affects Junos OS on EX Series and QFX Series:\n  *  23.4 version 23.4R2-S6,\n  *  24.2 version 24.2R2-S3.\n\n\nNo other Junos OS versions are affected.",
  "id": "GHSA-m7p5-cqg5-94p6",
  "modified": "2026-04-10T00:30:29Z",
  "published": "2026-04-10T00:30:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33773"
    },
    {
      "type": "WEB",
      "url": "https://kb.juniper.net/JSA107815"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:X/RE:M/U:X",
      "type": "CVSS_V4"
    }
  ]
}

CVE-2026-33773 (GCVE-0-2026-33773)

Vulnerability from cvelistv5 – Published: 2026-04-09 21:28 – Updated: 2026-04-09 21:28

Title

Junos OS: EX Series, QFX Series: If the same egress filter is configured on both an IRB and a physical interface one of those is not applied

Summary

An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks. When the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked. This issue affects Junos OS on EX Series and QFX Series: * 23.4 version 23.4R2-S6, * 24.2 version 24.2R2-S3. No other Junos OS versions are affected.

Severity ?

5.8 (Medium)


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

6.9 (Medium)


                        
                          CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/AU:Y/R:U/RE:M

CWE

CWE-1419 - Incorrect Initialization of Resource

Assigner

juniper

References

URL

Tags

https://kb.juniper.net/JSA107815

vendor-advisory

Impacted products

	Vendor	Product	Version
	Juniper Networks	Junos OS	Affected: 23.4R2-S6 , < 23.4R2-S7 (semver) Affected: 24.2R2-S3 , < 24.2R2-S4 (semver)

Date Public ?

2026-04-08 16:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "EX Series",
            "QFX Series"
          ],
          "product": "Junos OS",
          "vendor": "Juniper Networks",
          "versions": [
            {
              "lessThan": "23.4R2-S7",
              "status": "affected",
              "version": "23.4R2-S6",
              "versionType": "semver"
            },
            {
              "lessThan": "24.2R2-S4",
              "status": "affected",
              "version": "24.2R2-S3",
              "versionType": "semver"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "For a device to be affected the same filter needs to be applied as output to an IRB interface and a non-IRB interface as shown in the following example:\u003cbr\u003e\u003cbr\u003e\u003ctt\u003einterfaces \u0026lt;interface1\u0026gt; unit \u0026lt;unit1\u0026gt; family inet/inet6 filter output \u0026lt;filter\u0026gt;\u003cbr\u003e\u003cbr\u003evlans \u0026lt;vlan_name\u0026gt; vlan-id \u0026lt;vlan#\u0026gt;\u003cbr\u003evlans \u0026lt;vlan_name\u0026gt; l3-interface irb.\u0026lt;unit2\u0026gt;\u003cbr\u003e\n\n\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003e\n\n\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003einterfaces \u0026lt;interface2\u0026gt; unit \u0026lt;unit3\u0026gt; family ethernet-switching vlan members \u0026lt;vlan_name\u0026gt;\u003c/span\u003e\u003cbr\u003e\n\ninterfaces irb unit \u0026lt;unit2\u0026gt; family inet/inet6 filter output \u0026lt;filter\u0026gt;\u003c/span\u003e\u003cbr\u003e\n\n\u003c/tt\u003e\u003cbr\u003e"
            }
          ],
          "value": "For a device to be affected the same filter needs to be applied as output to an IRB interface and a non-IRB interface as shown in the following example:\n\ninterfaces \u003cinterface1\u003e unit \u003cunit1\u003e family inet/inet6 filter output \u003cfilter\u003e\n\nvlans \u003cvlan_name\u003e vlan-id \u003cvlan#\u003e\nvlans \u003cvlan_name\u003e l3-interface irb.\u003cunit2\u003e\n\n\n\n\ninterfaces \u003cinterface2\u003e unit \u003cunit3\u003e family ethernet-switching vlan members \u003cvlan_name\u003e\n\n\ninterfaces irb unit \u003cunit2\u003e family inet/inet6 filter output \u003cfilter\u003e"
        }
      ],
      "datePublic": "2026-04-08T16:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks.\u003cbr\u003e\u003cbr\u003eWhen the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.\u003cbr\u003e\u003cbr\u003eThis issue affects Junos OS on EX Series and QFX Series:\u003cbr\u003e\u003cul\u003e\u003cli\u003e23.4 version 23.4R2-S6,\u003c/li\u003e\u003cli\u003e24.2 version 24.2R2-S3.\u003c/li\u003e\u003c/ul\u003eNo other Junos OS versions are affected.\u003cbr\u003e\u003cbr\u003e"
            }
          ],
          "value": "An Incorrect Initialization of Resource vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on specific EX Series and QFX Series device allows an unauthenticated, network-based attacker to cause an integrity impact to downstream networks.\n\nWhen the same family inet or inet6 filter is applied on an IRB interface and on a physical interface as egress filter on EX4100, EX4400, EX4650 and QFX5120 devices, only one of the two filters will be applied, which can lead to traffic being sent out one of these interfaces which should have been blocked.\n\nThis issue affects Junos OS on EX Series and QFX Series:\n  *  23.4 version 23.4R2-S6,\n  *  24.2 version 24.2R2-S3.\n\n\nNo other Junos OS versions are affected."
        }
      ],
      "exploits": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Juniper SIRT is not aware of any malicious exploitation of this vulnerability."
            }
          ],
          "value": "Juniper SIRT is not aware of any malicious exploitation of this vulnerability."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "Automatable": "YES",
            "Recovery": "USER",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 6.9,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "LOW",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/AU:Y/R:U/RE:M",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "MODERATE"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-1419",
              "description": "CWE-1419 Incorrect Initialization of Resource",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-09T21:28:56.625Z",
        "orgId": "8cbe9d5a-a066-4c94-8978-4b15efeae968",
        "shortName": "juniper"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://kb.juniper.net/JSA107815"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "The following software releases have been updated to resolve this specific issue: 23.4R2-S7, 24.2R2-S4."
            }
          ],
          "value": "The following software releases have been updated to resolve this specific issue: 23.4R2-S7, 24.2R2-S4."
        }
      ],
      "source": {
        "advisory": "JSA107815",
        "defect": [
          "1900891"
        ],
        "discovery": "INTERNAL"
      },
      "title": "Junos OS: EX Series, QFX Series: If the same egress filter is configured on both an IRB and a physical interface one of those is not applied",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Two different workarounds are available:\u003cbr\u003e\u003cbr\u003e\n\n1. create the same filter but under a different name and apply that to one of the interfaces, so that each interface has a unique copy of the filter in question as shown in the following example:\u003cbr\u003e\u003cbr\u003e\u003ctt\u003euser@host# copy ... \u0026lt;filter\u0026gt; to ... \u0026lt;filter2\u0026gt;\u003cbr\u003euser@host# set\u0026nbsp;interfaces irb unit \u0026lt;unit2\u0026gt; family inet/inet6 filter output \u0026lt;filter2\u0026gt;\u003cbr\u003e\u003cbr\u003e\u003cbr\u003e\u003c/tt\u003e\n\n2. configure the filter as \"interface specific\" by adding the keyword to the filter definition:\u003cbr\u003e\u003ctt\u003e\u003cbr\u003e[ f\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eirewall family inet/inet6 filter \u0026lt;filter\u0026gt; interface-specific\u0026nbsp;\u003c/span\u003e]\u003cbr\u003e\u003c/tt\u003e \u003cbr\u003ewhich implicitly creates a copy of the original filter per applied interface."
            }
          ],
          "value": "Two different workarounds are available:\n\n\n\n1. create the same filter but under a different name and apply that to one of the interfaces, so that each interface has a unique copy of the filter in question as shown in the following example:\n\nuser@host# copy ... \u003cfilter\u003e to ... \u003cfilter2\u003e\nuser@host# set\u00a0interfaces irb unit \u003cunit2\u003e family inet/inet6 filter output \u003cfilter2\u003e\n\n\n\n\n2. configure the filter as \"interface specific\" by adding the keyword to the filter definition:\n\n[ firewall family inet/inet6 filter \u003cfilter\u003e interface-specific\u00a0]\n \nwhich implicitly creates a copy of the original filter per applied interface."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 0.1.0-dev"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8cbe9d5a-a066-4c94-8978-4b15efeae968",
    "assignerShortName": "juniper",
    "cveId": "CVE-2026-33773",
    "datePublished": "2026-04-09T21:28:56.625Z",
    "dateReserved": "2026-03-23T19:46:13.668Z",
    "dateUpdated": "2026-04-09T21:28:56.625Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-M7P5-CQG5-94P6

CVE-2026-33773 (GCVE-0-2026-33773)

Tags

Sightings

Nomenclature