# CVE-2019-0038: SRX Series: Crafted packets destined to fxp0 management interface on SRX340/SRX345 devices can lead to DoS

> Attackers can cause denial of service on Juniper SRX340/SRX345 devices by sending crafted packets to the management interface, exhausting buffer space.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7w57-fc78-9x64

## What is CVE-2019-0038?

CVE-2019-0038 is a medium-severity denial of service vulnerability in Juniper Junos, published on 10 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Crafted packets destined to the management interface (fxp0) of an SRX340 or SRX345 services gateway may create a denial of service (DoS) condition due to buffer space exhaustion. This issue only affects the SRX340 and SRX345 services gateways. No other products or platforms are affected by this vulnerability. Affected releases are Juniper Networks Junos OS: 15.1X49 versions prior to 15.1X49-D160 on SRX340/SRX345; 17.3 on SRX340/SRX345; 17.4 versions prior to 17.4R2-S3, 17.4R3 on SRX340/SRX345; 18.1 versions prior to 18.1R3-S1 on SRX340/SRX345; 18.2 versions prior to 18.2R2 on SRX340/SRX345; 18.3 versions prior to 18.3R1-S2, 18.3R2 on SRX340/SRX345. This issue does not affect Junos OS releases prior to 15.1X49 on any platform.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2019-0038?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2019-0038?

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

## Is CVE-2019-0038 being exploited?

There is no known exploitation of CVE-2019-0038 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-2019-0038 and fix it if it is affected.

What it is: CVE-2019-0038 is a medium-severity denial of service vulnerability in Juniper Junos, published on 10 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0038 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-2019-0038/ (Markdown: https://insights.sbomify.com/CVE-2019-0038/index.md)
```

## Sources

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

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