[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvz-0gCldUx-ZI3GtC0Ju9_zkC6o02XDyZo7KjW28VIQ":3},{"success":4,"data":5},true,{"vendor":6,"topVulnerabilitiesByEpss":37,"kevVulnerabilities":96,"topProductsByCves":97,"seoMetadata":102,"meta":111},{"vendorId":7,"vendorName":8,"productCount":9,"cveCount":10,"kevCount":11,"versionCount":12,"lastCveUpdate":13,"firstLetter":14,"products":15,"description":36},27492,"rsyslog",4,19,0,515,"2022-05-06","r",[16,20,26,31],{"id":17,"product_name":8,"version_count":18,"cve_count":19,"kev_count":11,"last_cve_update":13},139664,456,17,{"id":21,"product_name":22,"version_count":23,"cve_count":24,"kev_count":11,"last_cve_update":25},139663,"librelp",36,1,"2018-03-23",{"id":27,"product_name":28,"version_count":29,"cve_count":24,"kev_count":11,"last_cve_update":30},139665,"rsyslogd",15,"2005-09-27",{"id":32,"product_name":33,"version_count":34,"cve_count":11,"kev_count":11,"last_cve_update":35},139662,"libfastjson",8,null,"Rsyslog is a technology vendor with 4 tracked products and 19 known security vulnerabilities. Get comprehensive security analysis, vulnerability tracking, and threat intelligence for this vendor.",[38,47,54,61,65,71,76,80,85,90],{"cveId":39,"description":40,"publishedDate":41,"cvssScore":42,"cvssVersion":43,"severity":44,"isKev":45,"epssScore":46},"CVE-2011-3200","Stack-based buffer overflow in the parseLegacySyslogMsg function in tools\u002Fsyslogd.c in rsyslogd in rsyslog 4.6.x before 4.6.8 and 5.2.0 through 5.8.4 might allow remote attackers to cause a denial of service (application exit) via a long TAG in a legacy syslog message.","2011-09-06",5,"v2","Medium",false,0.20759,{"cveId":48,"description":49,"publishedDate":25,"cvssScore":50,"cvssVersion":51,"severity":52,"isKev":45,"epssScore":53},"CVE-2018-1000140","rsyslog librelp version 1.2.14 and earlier contains a Buffer Overflow vulnerability in the checking of x509 certificates from a peer that can result in Remote code execution. This attack appear to be exploitable a remote attacker that can connect to rsyslog and trigger a stack buffer overflow by sending a specially crafted x509 certificate.",9.8,"v3.0","Critical",0.09342,{"cveId":55,"description":56,"publishedDate":57,"cvssScore":58,"cvssVersion":43,"severity":59,"isKev":45,"epssScore":60},"CVE-2014-3634","rsyslog before 7.6.6 and 8.x before 8.4.1 and sysklogd 1.5 and earlier allows remote attackers to cause a denial of service (crash), possibly execute arbitrary code, or have other unspecified impact via a crafted priority (PRI) value that triggers an out-of-bounds array access.","2014-11-02",7.5,"High",0.07546,{"cveId":62,"description":63,"publishedDate":57,"cvssScore":42,"cvssVersion":43,"severity":44,"isKev":45,"epssScore":64},"CVE-2014-3683","Integer overflow in rsyslog before 7.6.7 and 8.x before 8.4.2 and sysklogd 1.5 and earlier allows remote attackers to cause a denial of service (crash) via a large priority (PRI) value.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-3634.",0.04585,{"cveId":66,"description":67,"publishedDate":68,"cvssScore":50,"cvssVersion":69,"severity":52,"isKev":45,"epssScore":70},"CVE-2019-17041","An issue was discovered in Rsyslog v8.1908.0. contrib\u002Fpmaixforwardedfrom\u002Fpmaixforwardedfrom.c has a heap overflow in the parser for AIX 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.","2019-10-07","v3.1",0.04445,{"cveId":72,"description":73,"publishedDate":13,"cvssScore":74,"cvssVersion":69,"severity":59,"isKev":45,"epssScore":75},"CVE-2022-24903","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.",8.1,0.03949,{"cveId":77,"description":78,"publishedDate":68,"cvssScore":50,"cvssVersion":69,"severity":52,"isKev":45,"epssScore":79},"CVE-2019-17042","An issue was discovered in Rsyslog v8.1908.0. contrib\u002Fpmcisconames\u002Fpmcisconames.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.",0.02983,{"cveId":81,"description":82,"publishedDate":83,"cvssScore":50,"cvssVersion":51,"severity":52,"isKev":45,"epssScore":84},"CVE-2017-12588","The zmq3 input and output modules in rsyslog before 8.28.0 interpreted description fields as format strings, possibly allowing a format string attack with unspecified impact.","2017-08-06",0.02834,{"cveId":86,"description":87,"publishedDate":88,"cvssScore":50,"cvssVersion":69,"severity":52,"isKev":45,"epssScore":89},"CVE-2019-17040","contrib\u002Fpmdb2diag\u002Fpmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.","2019-09-30",0.02415,{"cveId":91,"description":92,"publishedDate":93,"cvssScore":94,"cvssVersion":43,"severity":44,"isKev":45,"epssScore":95},"CVE-2013-4758","Double free vulnerability in the writeDataError function in the ElasticSearch plugin (omelasticsearch) in rsyslog before 7.4.2 and before 7.5.2 devel, when errorfile is set to local logging, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted JSON response.","2013-10-04",6.8,0.0233,[],[98,99,100,101],{"id":17,"product_name":8,"version_count":18,"cve_count":19,"kev_count":11,"last_cve_update":13},{"id":21,"product_name":22,"version_count":23,"cve_count":24,"kev_count":11,"last_cve_update":25},{"id":27,"product_name":28,"version_count":29,"cve_count":24,"kev_count":11,"last_cve_update":30},{"id":32,"product_name":33,"version_count":34,"cve_count":11,"kev_count":11,"last_cve_update":35},{"title":103,"metaDescription":104,"keywords":105,"structuredData":106},"Rsyslog - Security Vulnerabilities & Analysis | Precursor Intelligence","Comprehensive security analysis for Rsyslog covering 4 products with 19 tracked vulnerabilities. Real-time threat intelligence, CVE tracking, and security recommendations.","Rsyslog vulnerabilities, Rsyslog security, Rsyslog CVE, Rsyslog threat intelligence, vendor security analysis, cybersecurity threats, vulnerability management, CVE tracking",{"@context":107,"@type":108,"name":109,"description":104,"url":110},"https:\u002F\u002Fschema.org","Organization","Rsyslog","https:\u002F\u002Fprecursorintelligence.com\u002Fvendors\u002Frsyslog",{"totalProducts":9,"totalVulnerabilities":10,"kevVulnerabilities":11,"lastUpdated":13,"generatedAt":112,"apiVersion":113},"2026-10-18T20:37:48.618Z","3.0"]