# CVE-2017-2342: SRX Series: MACsec failure to report errors

> MACsec silently falls back to unencrypted links on unsupported ports, misleading administrators into believing traffic is secure.

- **Severity:** High 8.1 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 14 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c2jv-35gj-wg4v

## What is CVE-2017-2342?

CVE-2017-2342 is a high-severity vulnerability in Juniper Junos, published on 14 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MACsec feature on Juniper Networks Junos OS 15.1X49 prior to 15.1X49-D100 on SRX300 series does not report errors when a secure link can not be established. It falls back to an unencrypted link. This can happen when MACsec is configured on ports that are not capable of MACsec or when a secure link can not be established. This can mislead customers into believing that a link is secure. On SRX 300 series devices, prior to 15.1X49-D100, MACsec was only supported on control and fabric ports of SRX340 and SRX345 devices. SRX300 and and SRX320 did not have any MACsec capable ports. Configuring MACsec on ports that were not MACsec capable would have resulted in this issue. Affected releases are Juniper Networks Junos OS 15.1X49 prior to 15.1X49-D100 on SRX300 series.

Weakness: CWE-392 (Missing Report of Error Condition)

## Which versions are affected by CVE-2017-2342?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2017-2342?

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

## Is CVE-2017-2342 being exploited?

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

What it is: CVE-2017-2342 is a high-severity vulnerability in Juniper Junos, published on 14 Jul 2017. 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-2017-2342 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-2017-2342/ (Markdown: https://insights.sbomify.com/CVE-2017-2342/index.md)
```

## Sources

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

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