Skip to content
Noroxi
CVE-2019-17042· NVD / CVE Program· CNA mitre

An issue was discovered in Rsyslog v8.1908.0.

Noroxi assessment

Priority: Plan (action score 40/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.9% (FIRST EPSS); higher than 87% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: rsyslog (Alpine:v3.10) 8.1904.0-r1; rsyslog (Alpine:v3.11) 8.1908.0-r1; rsyslog (Alpine:v3.7) 8.31.0-r1.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to rsyslog (Alpine:v3.10) 8.1904.0-r1; rsyslog (Alpine:v3.11) 8.1908.0-r1; rsyslog (Alpine:v3.7) 8.31.0-r1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue was discovered in Rsyslog v8.1908.0. contrib/pmcisconames/pmcisconames.c has a heap overflow in the parser for Cisco log messages. The parser tries to locate a log message delimiter (in this case, a space or a colon), but fails to account for strings that do not satisfy this constraint. If the string does not match, then the variable lenMsg will reach the value zero and will skip the sanity check that detects invalid log messages. The message will then be considered valid, and the parser will eat up the nonexistent colon delimiter. In doing so, it will decrement lenMsg, a signed integer, whose value was zero and now becomes minus one. The following step in the parser is to shift left the contents of the message. To do this, it will call memmove with the right pointers to the target and destination strings, but the lenMsg will now be interpreted as a huge value, causing a heap overflow.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Oct 7, 2019
Updated
Jun 16, 2026
EPSS
2.9% · 87th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.9%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-17042

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for rsyslog records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
rsyslogrsyslog
fedoraprojectfedora
debiandebian linux
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux9.0
  • fedoraproject fedora30
  • fedoraproject fedora31
  • opensuse leap15.0
  • opensuse leap15.1
  • rsyslog rsyslog8.1908.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10rsyslogbefore 8.1904.0-r18.1904.0-r1
Alpine:v3.11rsyslogbefore 8.1908.0-r18.1908.0-r1
Alpine:v3.7rsyslogbefore 8.31.0-r18.31.0-r1
Alpine:v3.8rsyslogbefore 8.34.0-r18.34.0-r1
Alpine:v3.9rsyslogbefore 8.40.0-r48.40.0-r4
Debian:12rsyslogbefore 8.1910.0-18.1910.0-1
Debian:8rsyslogbefore 8.4.2-1+deb8u38.4.2-1+deb8u3
Debian:9rsyslogbefore 8.24.0-1+deb9u18.24.0-1+deb9u1
openSUSE:Leap 15.0rsyslogbefore 8.33.1-lp150.2.19.18.33.1-lp150.2.19.1
openSUSE:Leap 15.1rsyslogbefore 8.33.1-lp151.6.10.18.33.1-lp151.6.10.1
Red Hat:enterprise_linux:7::clientrsyslogbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-cryptobefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-debuginfobefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-docbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-elasticsearchbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-gnutlsbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-gssapibefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-kafkabefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-libdbibefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-mmauditbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-mmjsonparsebefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-mmkubernetesbefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-mmnormalizebefore 0:8.24.0-52.el70:8.24.0-52.el7
Red Hat:enterprise_linux:7::clientrsyslog-mmsnmptrapdbefore 0:8.24.0-52.el70:8.24.0-52.el7

+41

Same product

rsyslog: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-17041An issue was discovered in Rsyslog v8.1908.0.
    40Plan
  • CVE-2019-17040contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.
    40Plan
  • CVE-2017-12588The zmq3 input and output modules in rsyslog before 8.28.0 interpreted description fields as format strings, possibly allowing a format stri
    40Plan
  • CVE-2008-5617The ACL handling in rsyslog 3.12.1 to 3.20.0, 4.1.0, and 4.1.1 does not follow $AllowedSender directive, which allows remote attackers to by
    35Monitor
  • CVE-2022-24903Buffer overflow in TCP syslog server (receiver) components in rsyslog
    33Monitor
  • CVE-2026-61548Rsyslog: mmpstrucdata stack buffer overflow with oversized RFC5424 structured data
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:rsyslog8.1904.0-r1 · Alpine:v3.10Package registry (OSV)
debian:rsyslog8.1910.0-1 · Debian:12Package registry (OSV)
opensuse:rsyslog8.33.1-lp150.2.19.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:rsyslog0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-crypto0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-debuginfo0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-doc0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-elasticsearch0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-gnutls0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-gssapi0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-kafka0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-libdbi0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-mmaudit0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-mmjsonparse0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:rsyslog-relp0:8.24.0-52.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:rsyslog8.24.0-3.33.2 · SUSE:Linux Enterprise Desktop 12 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records