cisco rv340 firmware
productUScpe:2.3:o:cisco:rv340_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
12critical14high8medium0low
updated 2026-10-27
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2025-32433US | —OT critical | 98.9% (100th) | KEV | ✗no fix | 2025-04-16 | — |
| CVE-2022-20699US | critical9.8OT critical | 72.5% (99th) | KEV | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20708US | high8.0OT critical | 14.9% (97th) | KEV | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20701US | high7.8OT critical | 9.75% (95th) | KEV | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20703US | high8.0OT critical | 9.20% (95th) | KEV | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20700US | critical9.8OT critical | 5.66% (93rd) | KEV | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2023-20073US | critical9.8 | 90.1% (100th) | Exploit | ✗no fix | 2023-04-05 | ≤ 1.0.03.29 |
| CVE-2022-20705US | critical9.8 | 80.0% (100th) | Exploit | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20707US | high7.3 | 75.3% (100th) | Exploit | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2021-1472US | critical9.8 | 72.0% (99th) | Exploit | ✓1.0.03.21 | 2021-04-08 | < 1.0.03.21 |
| CVE-2021-1473US | critical9.8 | 64.4% (99th) | Exploit | ✓1.0.03.21 | 2021-04-08 | < 1.0.03.21 |
| CVE-2022-20706US | high8.1 | 5.57% (93rd) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20711US | critical9.8 | 4.92% (92nd) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20702US | high7.2 | 4.60% (92nd) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20749US | critical9.8 | 4.01% (90th) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20709US | high7.5 | 3.80% (90th) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20841US | critical9.0 | 3.33% (89th) | — | ✓1.0.03.26 | 2022-08-10 | < 1.0.03.26 |
| CVE-2020-3453US | medium6.8 | 3.08% (88th) | — | ✓1.0.03.19 | 2020-09-04 | < 1.0.03.19 |
| CVE-2022-20712US | critical9.8 | 3.03% (87th) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20710US | medium5.3 | 2.43% (84th) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20704US | medium4.8 | 2.30% (83rd) | — | ✗no fix | 2022-02-10 | ≤ 1.0.03.24 |
| CVE-2022-20753US | high7.2 | 2.22% (83rd) | — | ✓1.0.03.27 | 2022-05-04 | < 1.0.03.27 |
| CVE-2020-3451US | medium4.7 | 2.17% (82nd) | — | ✓1.0.03.19 | 2020-09-04 | < 1.0.03.19 |
| CVE-2022-20801US | high7.2 | 2.01% (81st) | — | ✓1.0.03.27 | 2022-05-04 | < 1.0.03.27 |
| CVE-2022-20827US | critical10.0 | 1.93% (80th) | — | ✓1.0.03.26 | 2022-08-10 | < 1.0.03.26 |
| CVE-2021-1414US | medium6.3 | 1.86% (79th) | — | ✓1.0.03.21 | 2021-04-08 | < 1.0.03.21 |
| CVE-2022-20842US | critical9.8 | 1.86% (79th) | — | ✓1.0.03.28 | 2022-08-10 | < 1.0.03.28 |
| CVE-2022-20799US | high7.2 | 1.69% (77th) | — | ✓1.0.03.27 | 2022-05-04 | < 1.0.03.27 |
| CVE-2021-1415US | medium6.3 | 1.61% (76th) | — | ✓1.0.03.21 | 2021-04-08 | < 1.0.03.21 |
| CVE-2021-1413US | medium6.3 | 1.61% (76th) | — | ✓1.0.0.3.21 | 2021-04-08 | < 1.0.0.3.21 |
| CVE-2023-20007US | high7.2 | 0.68% (52nd) | — | ✓1.0.03.29 | 2023-01-20 | < 1.0.03.29 |
| CVE-2021-1309US | high8.8 | 0.52% (44th) | — | ✗no fix | 2021-04-08 | 3 versions |
| CVE-2021-1308US | high7.4 | 0.43% (37th) | — | ✗no fix | 2021-04-08 | 3 versions |
| CVE-2021-1251US | high7.4 | 0.43% (37th) | — | ✗no fix | 2021-04-08 | 2 versions |
| CVE-2021-1520US | medium6.7 | 0.29% (21st) | — | ✓1.0.03.21 | 2021-05-06 | < 1.0.03.21 |