# CVE-2024-39533: Junos OS: QFX5000 Series and EX4600 Series: Output firewall filter is not applied if certain match criteria are used

> An attacker can bypass firewall filters on Juniper switches if unsupported match criteria are used, allowing unauthorized traffic to pass through.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5qpv-687p-m54h

## What is CVE-2024-39533?

CVE-2024-39533 is a medium-severity vulnerability in Juniper Junos, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Unimplemented or Unsupported Feature in the UI vulnerability in Juniper Networks Junos OS on QFX5000 Series and EX4600 Series allows an unauthenticated, network-based attacker to cause a minor integrity impact to downstream networks.If one or more of the following match conditions

ip-source-address
ip-destination-address
arp-type

which are not supported for this type of filter, are used in an ethernet switching filter, and then this filter is applied as an output filter, the configuration can be committed but the filter will not be in effect.

This issue affects Junos OS on QFX5000 Series and EX4600 Series:

  *  All version before 21.2R3-S7, 
  *  21.4 versions before 21.4R3-S6,
  *  22.1 versions before 22.1R3-S5,
  *  22.2 versions before 22.2R3-S3,
  *  22.3 versions before 22.3R3-S2, 
  *  22.4 versions before 22.4R3,
  *  23.2 versions before 23.2R2.

Please note that the implemented fix ensures these unsupported match conditions cannot be committed anymore.

Weakness: CWE-447 (Unimplemented or Unsupported Feature in UI)

## Which versions are affected by CVE-2024-39533?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2024-39533?

No fix has been published for CVE-2024-39533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-39533 being exploited?

There is no known exploitation of CVE-2024-39533 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39533 and fix it if it is affected.

What it is: CVE-2024-39533 is a medium-severity vulnerability in Juniper Junos, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-39533 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-39533/ (Markdown: https://insights.sbomify.com/CVE-2024-39533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39533
- OSV: https://osv.dev/vulnerability/CVE-2024-39533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-39533/
Summaries are generated and may contain mistakes; the official description above is the record.