# CVE-2024-30407: [Child CVE] JCNR and cRPD: Hard-coded SSH host keys in cRPD may allow Person-in-the-Middle (PitM) attacks

> Hardcoded SSH host keys in Juniper JCNR and cRPD allow attackers to perform Person-in-the-Middle attacks, leading to complete container compromise.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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:** 12 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-wp5q-4qc3-582g

## What is CVE-2024-30407?

CVE-2024-30407 is a critical vulnerability in Juniper Cloud Native Router (JCNR), published on 12 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Use of a Hard-coded Cryptographic Key vulnerability in Juniper Networks Juniper Cloud Native Router (JCNR) and containerized routing Protocol Deamon (cRPD) products allows an attacker to perform Person-in-the-Middle (PitM) attacks which results in complete compromise of the container. 

Due to hardcoded SSH host keys being present on the container, a PitM attacker can intercept SSH traffic without being detected. 

This issue affects Juniper Networks JCNR:
  *  All versions before 23.4.

This issue affects Juniper Networks cRPD:
  *  All versions before 23.4R1.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2024-30407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30407 is a critical vulnerability in Juniper Cloud Native Router (JCNR), published on 12 Apr 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-30407 in the wild and no public exploit code.

Affected product: Juniper Cloud Native Router (JCNR). 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-30407/ (Markdown: https://insights.sbomify.com/CVE-2024-30407/index.md)
```

## Sources

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

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