[Child CVE] JCNR and cRPD: Hard-coded SSH host keys in cRPD may allow Person-in-the-Middle (PitM) attacks
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Juniper Networks, Inc. | cRPD | unaffected |
|
||||||
| Juniper Networks, Inc. | Juniper Cloud Native Router (JCNR) | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
The following software releases have been updated to resolve this specific issue: JCNR: 23.4, and all subsequent releases. cRPD: 23.4R1, and all subsequent releases.
Vendor Workaround
Remove the hard coded keys using: "rm -rf /etc/ssh/ssh_host_*" and then run "ssh-keygen -A" to generate new host keys.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-28328 | 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. |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.676% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.
No data.