LiveActive security incident?Get immediate response
CVE Record

CVE-2019-17040: contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is...

contrib/pmdb2diag/pmdb2diag.c in Rsyslog v8.1908.0 allows out-of-bounds access because the level length is mishandled.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-17040 is an out-of-bounds access issue in Rsyslog v8.1908.0’s pmdb2diag diagnostic code. The available record does not provide a CVSS score, confirmed impact, or evidence of active exploitation. Treat it as a targeted maintenance risk unless this diagnostic tool is exposed to untrusted input.

Executive priority

Prioritize as a routine remediation item unless pmdb2diag is used in production workflows or receives untrusted input. Lack of severity scoring and exploitation evidence lowers urgency, but logging infrastructure should still be kept current.

Technical view

The CVE describes mishandling of a level length value in contrib/pmdb2diag/pmdb2diag.c, causing out-of-bounds access. The source bundle identifies Rsyslog v8.1908.0 but does not enumerate affected downstream packages, exploitability conditions, or fixed versions. Fedora advisories and an upstream pull request are cited.

Likely exposure

Exposure appears limited to environments with affected Rsyslog code, especially where pmdb2diag is present or used against externally supplied or untrusted diagnostic data. The bundle does not show that normal syslog ingestion paths are affected.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not listed as KEV. The available information is too sparse to determine whether exploitation is practical, remote, local, or only crash-oriented.

Researcher notes

The public record is thin: no CVSS vector, CWE, exploit status, or detailed affected-product matrix is provided. Analysis should focus on the upstream pull request, changelog, and downstream package advisories before assigning internal severity.

Mitigation direction

  • Identify systems running Rsyslog v8.1908.0 or downstream builds containing pmdb2diag.
  • Review upstream Rsyslog and Fedora advisories for corrected package versions.
  • Apply vendor or distribution rsyslog updates where available.
  • Avoid running pmdb2diag on untrusted input until vendor guidance is confirmed.
  • Limit access to diagnostic tooling on production logging hosts.

Validation and detection

  • Inventory Rsyslog versions across servers and container images.
  • Check whether pmdb2diag is installed, packaged, or used operationally.
  • Compare installed packages against Fedora or vendor advisory status.
  • Confirm updated packages include the upstream fix referenced by PR 3875.
  • Review operational procedures for untrusted diagnostic file handling.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-17040 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.