CVE-2017-9465

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The yr_arena_write_data function in YARA 3.6.1 allows remote attackers to cause a denial of service (buffer over-read and application crash) or obtain sensitive information from process memory via a crafted file that is mishandled in the yr_re_fast_exec function in libyara/re.c and the _yr_scan_match_callback function in libyara/scan.c.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 6, 2017

Last Modified

June 17, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuyara-doc (3.9.0-1ubuntu0.1~esm1) @ focal2026-05-22ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
yara—
  • every version up to 3.6.2+dfsg-1: fixed in 3.6.2+dfsg-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
yara—
  • every version up to 3.6.2+dfsg-1: fixed in 3.6.2+dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
yara—
  • every version up to 3.6.2+dfsg-1: fixed in 3.6.2+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
yara—
  • every version up to 3.6.2+dfsg-1: fixed in 3.6.2+dfsg-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 27× 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 84 of 179 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. 16 repeat rows among the latest 100 are merged into the row they repeat. The 95 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-9465?
CVE-2017-9465 is a high-severity vulnerability; its CVE record was published on June 6, 2017. The yrarenawritedata function in YARA 3.6.1 allows remote attackers to cause a denial of service (buffer over-read and application crash) or obtain sensitive information from process memory via a crafted file that is mishandled in the yrrefastexec function in libyara/re.c and the…
When was the CVE record for CVE-2017-9465 published?
The CVE record for CVE-2017-9465 was published on June 6, 2017. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-9465 actively exploited?
CVE-2017-9465 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-9465?
CVE-2017-9465 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2017-9465?
A fix for CVE-2017-9465 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-9465

Explore →

Is Your Infrastructure Affected by CVE-2017-9465?

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

Book a Demo →Browse All CVEs