Juniper Cloud Native Router (Jcnr)
Approved changes feed: RSS · Atom
cpe:2.3:a:juniper_networks,_inc.:juniper_cloud_native_router_(jcnr):*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Juniper Networks, Inc. (c5fb7376-0b35-5d31-8984-a18994efb618) |
|---|---|
| Product | Juniper Cloud Native Router (Jcnr) (4968cf26-ed49-597e-b7f5-e4fb6317fbf3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-30407 |
vulnerable | 2026-06-08 06:35:30.270317 |
[Child CVE] JCNR and cRPD: Hard-coded SSH host keys in cRPD may allow Person-in-the-Middle (PitM) attacks
HIGH (8.1)
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.
Published: 2024-04-12T15:03:40.856Z
Updated: 2024-08-02T01:32:07.279Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.