CVE-2022-3970

CRITICALNVD 6.39.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-11-13. NVD baseline CVSS 6.3; sources differ by 3.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2022-43302 (ENISA EUVD) · GHSA-44v9-23w3-fv66 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability was found in LibTIFF. It has been classified as critical. This affects the function TIFFReadRGBATileExt of the file libtiff/tif_getimage.c. The manipulation leads to integer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 227500897dfb07fb7d27f7aa570050e62617e3be. It is recommended to apply a patch to fix this issue. The identifier VDB-213549 was assigned to this vulnerability.

CVSS v3
6.3
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.7%
EPSS %ILE
77th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 low or medium mission impact; Track* at high (mission-essential systems).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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 public PoC (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.

The score's inputs: 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

November 13, 2022

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Oct 13, 2026
Patch available.
Web page

TIFFReadRGBATileExt(): fix (unsigned) integer overflow on strips/tiles > 2 GB (22750089) · Commits · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/commit/227500897dfb07fb7d27f7aa570050e62617e3be
Web page

About the security content of macOS Ventura 13.5 - Apple Support

https://support.apple.com/kb/HT213843
Web page

About the security content of iOS 16.6 and iPadOS 16.6 - Apple Support

https://support.apple.com/kb/HT213841
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3278-1] tiff security update

https://lists.debian.org/debian-lts-announce/2023/01/msg00018.html

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibtiff-doc (4.0.6-1ubuntu0.8+esm8) @ xenial2026-11-11ubuntu
ubuntulibtiff-doc (4.4.0-4ubuntu3.2) @ kinetic2026-11-11ubuntu
ubuntulibtiff-doc (4.0.6-1ubuntu0.8+esm9) @ xenial2026-11-11ubuntu
redhatlibtiff-0:4.0.9-27.el82023-05-16redhat
redhatlibtiff-0:4.4.0-7.el92023-05-09redhat

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

(16 across 16 ecosystems)
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-r1: fixed in 4.4.0-r1
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-r1: fixed in 4.4.0-r1
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-r1: fixed in 4.4.0-r1
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-r2: fixed in 4.4.0-r2
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.5.0-r0: fixed in 4.5.0-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.0.10+git190814-1 ... 4.1.0-1 (11 versions)
  • every version up to 4.1.0+git191117-2~deb10u5: fixed in 4.1.0+git191117-2~deb10u5
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.2.0-1, 4.2.0-1+deb11u1, 4.2.0-1+deb11u2
  • every version up to 4.2.0-1+deb11u3: fixed in 4.2.0-1+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-6: fixed in 4.4.0-6
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-6: fixed in 4.4.0-6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
tiff—
  • every version up to 4.4.0-6: fixed in 4.4.0-6
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 91× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 315 rows 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. None are among the latest 100 rows. The 215 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 21:02 UTCEchelonGraph re-scored
  2. 2026-11-12 21:02 UTCVendor advisory
  3. 2026-11-12 21:02 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-12 16:30 UTCEPSS rescoreEPSS 1.7% · 77th percentile
  5. 2026-11-11 22:11 UTCEchelonGraph re-scored
  6. 2026-11-11 22:11 UTCVendor advisory
  7. 2026-11-11 22:11 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-11 16:33 UTCEPSS rescoreEPSS 1.7% · 77th percentile
  9. 2026-11-10 23:14 UTCEchelonGraph re-scored
  10. 2026-11-10 23:14 UTCVendor advisory
  11. 2026-11-10 23:14 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-10 16:36 UTCEPSS rescoreEPSS 1.7% · 77th percentile
  13. 2026-11-10 00:22 UTCEchelonGraph re-scored
  14. 2026-11-10 00:22 UTCVendor advisory
  15. 2026-11-10 00:22 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-09 16:30 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  17. 2026-11-09 01:31 UTCEchelonGraph re-scored
  18. 2026-11-09 01:31 UTCVendor advisory
  19. 2026-11-09 01:31 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-08 16:34 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  21. 2026-11-08 02:40 UTCEchelonGraph re-scored
  22. 2026-11-08 02:40 UTCVendor advisory
  23. 2026-11-08 02:40 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-07 16:34 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  25. 2026-11-07 03:48 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-07 03:48 UTCVendor advisory
  2. 2026-11-07 03:48 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  4. 2026-11-06 04:57 UTCEchelonGraph re-scored
  5. 2026-11-06 04:57 UTCVendor advisory
  6. 2026-11-06 04:57 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-05 16:32 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  8. 2026-11-05 06:06 UTCEchelonGraph re-scored
  9. 2026-11-05 06:06 UTCVendor advisory
  10. 2026-11-05 06:06 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-04 16:30 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  12. 2026-11-04 07:13 UTCEchelonGraph re-scored
  13. 2026-11-04 07:13 UTCVendor advisory
  14. 2026-11-04 07:13 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-04 06:25 UTCOSV refresh
  16. 2026-11-03 16:39 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  17. 2026-11-03 08:19 UTCEchelonGraph re-scored
  18. 2026-11-03 08:19 UTCVendor advisory
  19. 2026-11-03 08:19 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  21. 2026-11-02 09:27 UTCEchelonGraph re-scored
  22. 2026-11-02 09:27 UTCVendor advisory
  23. 2026-11-02 09:27 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-01 10:36 UTCEchelonGraph re-scored
  25. 2026-11-01 10:36 UTCVendor advisory
  26. 2026-11-01 10:36 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  28. 2026-10-31 11:44 UTCEchelonGraph re-scored
  29. 2026-10-31 11:44 UTCVendor advisory
  30. 2026-10-31 11:44 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  32. 2026-10-30 12:53 UTCEchelonGraph re-scored
  33. 2026-10-30 12:53 UTCVendor advisory
  34. 2026-10-30 12:52 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  36. 2026-10-29 13:59 UTCEchelonGraph re-scored
  37. 2026-10-29 13:59 UTCVendor advisory
  38. 2026-10-29 13:59 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  40. 2026-10-28 15:08 UTCEchelonGraph re-scored
  41. 2026-10-28 15:08 UTCVendor advisory
  42. 2026-10-28 15:08 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  44. 2026-10-27 16:17 UTCVendor advisory
  45. 2026-10-27 16:16 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-26 17:15 UTCEchelonGraph re-scored
  47. 2026-10-26 17:15 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  49. 2026-10-25 18:04 UTCVendor advisory
  50. 2026-10-25 18:04 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-25 18:01 UTCEchelonGraph re-scored
  52. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  53. 2026-10-24 18:45 UTCEchelonGraph re-scored
  54. 2026-10-24 18:45 UTCVendor advisory
  55. 2026-10-24 18:45 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  57. 2026-10-23 19:54 UTCEchelonGraph re-scored
  58. 2026-10-23 19:54 UTCVendor advisory
  59. 2026-10-23 19:54 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  61. 2026-10-22 21:01 UTCEchelonGraph re-scored
  62. 2026-10-22 21:01 UTCVendor advisory
  63. 2026-10-22 21:01 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  65. 2026-10-21 22:10 UTCEchelonGraph re-scored
  66. 2026-10-21 22:10 UTCVendor advisory
  67. 2026-10-21 22:10 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.3% · 71st percentile
  69. 2026-10-20 23:16 UTCEchelonGraph re-scored
  70. 2026-10-20 23:16 UTCVendor advisory
  71. 2026-10-20 23:16 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  73. 2026-10-20 00:25 UTCEchelonGraph re-scored
  74. 2026-10-20 00:25 UTCVendor advisory
  75. 2026-10-20 00:25 UTCGHSA enrichmentGHSA-44v9-23w3-fv66 · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2022-3970?
CVE-2022-3970 is a critical-severity vulnerability; its CVE record was published on November 13, 2022. A vulnerability was found in LibTIFF. It has been classified as critical. This affects the function TIFFReadRGBATileExt of the file libtiff/tif_getimage.c. The manipulation leads to integer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and…
When was the CVE record for CVE-2022-3970 published?
The CVE record for CVE-2022-3970 was published on November 13, 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-3970 actively exploited?
CVE-2022-3970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (77th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-3970?
CVE-2022-3970 has a CVSS v3 base score of 6.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-3970?
A fix for CVE-2022-3970 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-3970 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-3970

Explore →

Is Your Infrastructure Affected by CVE-2022-3970?

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