CVE-2017-18379

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.8%CVSS: 9.8Exploit: None knownExposed services: —

A fix is available — apply it.

In the Linux kernel before 4.14, an out of boundary access happened in drivers/nvme/target/fc.c.

Internet exposure

The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation3% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.8%
EPSS %ILE
85th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 27, 2019

Last Modified

November 21, 2024

Vendor Advisories for CVE-2017-18379

Vendor advisories for this CVE are temporarily unavailable — the list could not be loaded just now. That is not a sign that none exist; please retry shortly.

Weakness Classification(1)

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

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2017-18379?
CVE-2017-18379 is a critical vulnerability published on July 27, 2019. In the Linux kernel before 4.14, an out of boundary access happened in drivers/nvme/target/fc.c.
When was CVE-2017-18379 disclosed?
CVE-2017-18379 was first published on July 27, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-18379 actively exploited?
CVE-2017-18379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-18379?
CVE-2017-18379 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-18379?
A fix for CVE-2017-18379 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-18379

Explore →

Is Your Infrastructure Affected by CVE-2017-18379?

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