CVE-2022-1318

MEDIUMNVD 6.26.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.2 under NVD CVSS v3. EPSS exploit probability: 0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2022-04-21) is not newer than that change (2024-11-21), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
6.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.2Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)) lists Interlogix ComNav versions up to and including 3002-19 as affected. No release containing a fix is confirmed on record.

Hills ComNav version 3002-19 suffers from a weak communication channel. Traffic across the local network for the configuration pages can be viewed by a malicious actor. The size of certain communications packets are predictable. This would allow an attacker to learn the state of the system if they can observe the traffic. This would be possible even if the traffic were encrypted, e.g., using WPA2, as the packet sizes would remain observable. The communication encryption scheme is theoretically sound, but is not strong enough for the level of protection required.

CVSS v3
6.2
EG Score
6.2MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity62% × 45%
Impact severity (EG Severity): CVSS 6.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.2): severity, escalated by confirmed exploitation. This CVE's 6.2 is its impact severity (EG Severity), not escalated.

EG Severity
6.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 20, 2022

Last Modified

November 21, 2024

References (1)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 143 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 55 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  2. 2026-10-22 16:29 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  3. 2026-10-20 16:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  4. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  5. 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  6. 2026-10-18 08:47 UTCEG score recompute
  7. 2026-10-16 16:34 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-10-13 16:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  10. 2026-10-12 19:03 UTCEG score recompute
  11. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-11 23:29 UTCEG score recompute
  13. 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  14. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  15. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  17. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-09-30 15:47 UTCEG score recompute
  21. 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  22. 2026-09-29 15:15 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  23. 2026-09-26 15:54 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  24. 2026-09-26 00:21 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  25. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
Show 63 more
  1. 2026-09-21 20:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  2. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  3. 2026-09-18 19:24 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  4. 2026-09-17 19:23 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  5. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  6. 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  7. 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-09-08 21:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-09-07 15:58 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-09-06 13:45 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-09-05 15:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-09-04 13:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-09-02 14:09 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-09-01 13:51 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-08-30 19:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-08-30 01:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-08-28 21:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-08-27 14:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-08-26 14:43 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-08-24 14:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-08-21 23:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-08-20 22:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-08-19 17:01 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-08-18 13:45 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-08-17 13:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  27. 2026-08-16 14:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  28. 2026-08-16 02:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-08-15 01:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  30. 2026-08-13 21:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  31. 2026-08-11 13:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  32. 2026-08-08 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  33. 2026-08-07 16:24 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  34. 2026-08-06 13:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  35. 2026-08-05 19:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  36. 2026-08-04 15:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  37. 2026-08-01 04:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  38. 2026-07-30 16:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  39. 2026-07-30 01:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-07-28 15:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  41. 2026-07-25 14:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  42. 2026-07-24 14:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-07-23 14:16 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  44. 2026-07-23 02:07 UTCEG score recompute
  45. 2026-07-22 22:53 UTCEG score recompute▲ 0.70
  46. 2026-07-22 14:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-07-21 15:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  48. 2026-07-20 17:05 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  49. 2026-07-19 02:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-07-16 17:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  51. 2026-07-15 16:55 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  52. 2026-07-13 22:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  53. 2026-07-13 06:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  54. 2026-07-12 05:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-07-11 08:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  56. 2026-07-09 19:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-07-08 15:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  58. 2026-07-07 13:43 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  59. 2026-07-06 16:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  60. 2026-07-04 06:29 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  61. 2026-07-01 15:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-06-29 14:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  63. 2026-06-28 14:05 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-1318?
CVE-2022-1318 is a medium-severity vulnerability; its CVE record was published on April 20, 2022. Hills ComNav version 3002-19 suffers from a weak communication channel. Traffic across the local network for the configuration pages can be viewed by a malicious actor. The size of certain communications packets are predictable. This would allow an attacker to learn the state of the system if they…
When was the CVE record for CVE-2022-1318 published?
The CVE record for CVE-2022-1318 was published on April 20, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-1318 actively exploited?
CVE-2022-1318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-1318?
CVE-2022-1318 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2022-1318?
No fix for CVE-2022-1318 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)) lists Interlogix ComNav versions up to and including 3002-19 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-1318

Explore →

Is Your Infrastructure Affected by CVE-2022-1318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs