CVE-2022-50975
Unauthenticated remote attacker hijacks an existing session to gain full device access (Ethernet-enabled).
Is CVE-2022-50975 being exploited?
Not confirmed. CVE-2022-50975 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2022-50975?
CVE-2022-50975 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-50975?
Not known from our data. No patch reference has been recorded for CVE-2022-50975, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2022-50975 affect?
CVE-2022-50975 affects Devices with Ethernet-configured sessions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2022-50975?
Patch when available; mitigate by disabling Ethernet-exposed sessions and restricting remote access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote session hijack enables full device control via network if Ethernet config is enabled.
Immediate action required
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
- affected>= 2.1.1340 and <= 2.1.1387
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.