TZInfo is a Ruby library that provides access to time zone data and allows times to be converted using time zone rules. Versions prior to 0.36.1, as well as those prior to 1.2.10 when used with the Ruby data source tzinfo-data, are vulnerable to relative path traversal. With the Ruby data source, time zones are defined in Ruby files. There is one file per time zone. Time zone files are loaded with require on demand. In the affected versions, TZInfo::Timezone.get fails to validate time zone identifiers correctly, allowing a new line character within the identifier. With Ruby version 1.9.3 and later, TZInfo::Timezone.get can be made to load unintended files with require, executing them within the Ruby process. Versions 0.3.61 and 1.2.10 include fixes to correctly validate time zone identifiers. Versions 2.0.0 and later are not vulnerable. Version 0.3.61 can still load arbitrary files from the Ruby load path if their name follows the rules for a valid time zone identifier and the file has a prefix of tzinfo/definition within a directory in the load path. Applications should ensure that untrusted files are not placed in a directory on the load path. As a workaround, the time zone identifier can be validated before passing to TZInfo::Timezone.get by ensuring it matches the regular expression \A[A-Za-z0-9+\-_]+(?:\/[A-Za-z0-9+\-_]+)*\z.
CVE-2022-31163
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-07-21. NVD baseline CVSS 7.5; sources differ by 0.0.
Also known asEUVD-2022-6242 (ENISA EUVD) · GHSA-5cm2-9h8c-rvfx (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 50EG Risk 50/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 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, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.4%
- EPSS %ILE
- 84th
- 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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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
July 22, 2022
Last Modified
November 21, 2024
References (7)
- security-advisories@github · CVE Programhttps://github.com/tzinfo/tzinfo/commit/9905ca93abf7bf3e387bd592406e403cd18334c7Patch · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/tzinfo/tzinfo/commit/9eddbb5c0e682736f61d0dd803b6031a5db9eadfPatch · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/tzinfo/tzinfo/releases/tag/v0.3.61Release Notes · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/tzinfo/tzinfo/releases/tag/v1.2.10Release Notes · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/tzinfo/tzinfo/security/advisories/GHSA-5cm2-9h8c-rvfxExploit · Third Party Advisory
- security-advisories@github · CVE Programhttps://lists.debian.org/debian-lts-announce/2022/08/msg00009.htmlMailing List · Third Party Advisory
- CVE Programhttps://lists.debian.org/debian-lts-announce/2024/09/msg00008.html
Vendor Advisories for CVE-2022-31163(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2023:2097Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.13 Release
- RHSA-2023:1486Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Gluster Storage web-admin-build security update
- RHSA-2022:7242Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.11.4 Async Security Update
Patch Availability(5)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | rubygem-tzinfo-0:2.0.5-1.el8sat | 2023-05-03 | redhat |
| redhat | rubygem-tzinfo-0:1.2.10-1.el7rhgs | 2023-03-28 | redhat |
| redhat | rubygem-tzinfo-0:1.2.10-1.el8sat | 2022-10-27 | redhat |
| rubygems | tzinfo @ 0.3.61 (fixes < 0.3.61) | — | ghsa |
| rubygems | tzinfo @ 1.2.10 (fixes >= 1.0.0, < 1.2.10) | — | ghsa |
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
(6 across 6 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ruby-tzinfo | 1.2.5-1 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ruby-tzinfo | 1.2.6-1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ruby-tzinfo | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ruby-tzinfo | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ruby-tzinfo | — |
| — |
RubyGems(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tzinfo | 1.0.0 ... 1.2.9 (13 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 41× 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 99 of 220 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-11-01 08:26 UTCGHSA enrichmentGHSA-5cm2-9h8c-rvfx · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 08:26 UTCEG score recompute
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-29 03:15 UTCEG score recompute
- 2026-10-29 03:15 UTCVendor advisory
- 2026-10-29 01:25 UTCOSV refresh
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-26 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-25 18:08 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-21 07:20 UTCEG score recompute
- 2026-10-21 07:20 UTCVendor advisory
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-18 08:35 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
Show 74 moreShow fewer
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-16 08:24 UTCOSV refresh
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-12 18:54 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-11 23:19 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-30 15:55 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-28 13:48 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-24 16:16 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 2.4% · 82nd percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-05 08:44 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-23 00:16 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-18 19:07 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 2.2% · 81st percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 2.2% · 80th percentile
- 2026-08-03 14:57 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 2.2% · 80th percentile
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2022:7242 · redhat:RHSA-2023:1486 · redhat:RHSA-2023:2097
- CVE-2022-30122EG 7.5HIGH
- CVE-2022-30123EG 10.0CRITICAL
- CVE-2022-32224EG 9.8CRITICAL
- CVE-2022-42889EG 9.8EPSS p100CRITICAL
- CVE-2022-33980EG 9.8EPSS p99CRITICAL
- CVE-2022-24790EG 9.1CRITICAL
- CVE-2022-1471NVD 8.3EG 9.0EPSS p100CRITICAL
- CVE-2023-24580NVD 7.5EG 8.4EPSS p99HIGH
- CVE-2023-23969NVD 7.5EG 8.0EPSS p99HIGH
- CVE-2021-46877EG 7.5HIGH
Same CWE
10 shownCWE-23 · CWE-22
Frequently asked(5)
What is CVE-2022-31163?
When was the CVE record for CVE-2022-31163 published?
Is CVE-2022-31163 actively exploited?
What is the CVSS score of CVE-2022-31163?
How do I remediate CVE-2022-31163?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31163
Is Your Infrastructure Affected by CVE-2022-31163?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.