CVE-2022-24903

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 3.9% (90th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2022-29662 (ENISA EUVD)Source: ENISA EUVD

8.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: 3.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Rsyslog is a rocket-fast system for log processing. Modules for TCP syslog reception have a potential heap buffer overflow when octet-counted framing is used. This can result in a segfault or some other malfunction. As of our understanding, this vulnerability can not be used for remote code execution. But there may still be a slight chance for experts to do that. The bug occurs when the octet count is read. While there is a check for the maximum number of octets, digits are written to a heap buffer even when the octet count is over the maximum, This can be used to overrun the memory buffer. However, once the sequence of digits stop, no additional characters can be added to the buffer. In our opinion, this makes remote exploits impossible or at least highly complex. Octet-counted framing is one of two potential framing modes. It is relatively uncommon, but enabled by default on receivers. Modules imtcp, imptcp, imgssapi, and imhttp are used for regular syslog message reception. It is best practice not to directly expose them to the public. When this practice is followed, the risk is considerably lower. Module imdiag is a diagnostics module primarily intended for testbench runs. We do not expect it to be present on any production installation. Octet-counted framing is not very common. Usually, it needs to be specifically enabled at senders. If users do not need it, they can turn it off for the most important modules. This will mitigate the vulnerability.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation4.0% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
3.9%
EPSS %ILE
90th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
3.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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: 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 or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (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

May 6, 2022

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3016-1] rsyslog security update

https://lists.debian.org/debian-lts-announce/2022/05/msg00028.html
GitHub advisoryMentions a patch (unverified)

Potential heap buffer overflow in TCP syslog server (receiver) components · Advisory · rsyslog/rsyslog · GitHub

https://github.com/rsyslog/rsyslog/security/advisories/GHSA-ggw7-xr6h-mmr8
GitHub commit Patch Available

commit f211042ecbb4 (rsyslog/rsyslog)

Patch available: rsyslog/rsyslog v8.2604.0 (contains commit f211042ecbb4)

https://github.com/rsyslog/rsyslog/commit/f211042ecbb472f9d8beb4678a65d272b6f07705
Web page

[SECURITY] [DSA 5150-1] rsyslog security update

https://www.debian.org/security/2022/dsa-5150
Web page

NetApp Product Security

https://security.netapp.com/advisory/ntap-20221111-0002/
Web page

[SECURITY] Fedora 35 Update: rsyslog-8.2204.0-1.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GMNNXLCU2UORRVSZO24HL4KMVPK5PHVW/

Vendor Advisories for CVE-2022-24903(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntursyslog-gnutls (8.16.0-1ubuntu3.1+esm2) @ xenial2026-10-28ubuntu
ubuntursyslog-kafka (8.2001.0-1ubuntu1.3) @ focal2026-10-28ubuntu
redhatredhat-virtualization-host-0:4.3.23-20220622.0.el7_92022-07-01redhat
redhatredhat-virtualization-host-0:4.5.0-202205291010_8.62022-06-03redhat
redhatrsyslog7-0:7.4.10-7.el6_10.12022-05-31redhat
redhatrsyslog-0:8.1911.0-3.el8_2.12022-05-30redhat
redhatrsyslog-0:8.1911.0-7.el8_4.32022-05-30redhat
redhatrsyslog-0:8.24.0-57.el7_9.32022-05-30redhat
redhatrsyslog-0:8.2102.0-101.el9_0.12022-05-30redhat
redhatrsyslog-0:8.37.0-13.el8_1.12022-05-30redhat
redhatrsyslog-0:8.2102.0-7.el8_6.12022-05-30redhat

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

(19 across 19 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2004.0-r2: fixed in 8.2004.0-r2
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2012.0-r3: fixed in 8.2012.0-r3
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2012.0-r3: fixed in 8.2012.0-r3
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2108.0-r2: fixed in 8.2108.0-r2
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-r0: fixed in 8.2204.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.1901.0-1, 8.1901.0-1+deb10u1
  • every version up to 8.1901.0-1+deb10u2: fixed in 8.1901.0-1+deb10u2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.2102.0-2
  • every version up to 8.2102.0-2+deb11u1: fixed in 8.2102.0-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-1: fixed in 8.2204.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-1: fixed in 8.2204.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog—
  • every version up to 8.2204.1-1: fixed in 8.2204.1-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.24.0-1, 8.24.0-1+deb9u1
  • every version up to 8.24.0-1+deb9u2: fixed in 8.24.0-1+deb9u2
—

Weakness Classification(2)

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

Additional Vendor Advisories

(7)

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 8× in last 7d / 38× 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 98 of 190 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2022-24903?
CVE-2022-24903 is a high-severity vulnerability; its CVE record was published on May 6, 2022. Rsyslog is a rocket-fast system for log processing. Modules for TCP syslog reception have a potential heap buffer overflow when octet-counted framing is used. This can result in a segfault or some other malfunction. As of our understanding, this vulnerability can not be used for remote code…
When was the CVE record for CVE-2022-24903 published?
The CVE record for CVE-2022-24903 was published on May 6, 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-24903 actively exploited?
CVE-2022-24903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.9% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24903?
CVE-2022-24903 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2022-24903?
A fix for CVE-2022-24903 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-24903 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-24903

Explore →

Is Your Infrastructure Affected by CVE-2022-24903?

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

Book a Demo →Browse All CVEs