dbcve.org
LogstashApplication · Elastic

CVE-2019-7612

CRITICAL · 9.8 CVSS v3.1 Published 2019-03-25
Fix available
A fix is available. Upgrade to 5.6.15 / 6.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A sensitive data disclosure flaw was found in the way Logstash versions before 5.6.15 and 6.6.1 logs malformed URLs. If a malformed URL is specified as part of the Logstash configuration, the credentials for the URL could be inadvertently logged as part of the error message.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Logstash versions before 5.6.15 and 6.6.1 have a sensitive data disclosure flaw where malformed URLs containing credentials (e.g., https://user:password@hostname) specified in Logstash configuration are logged in full as part of error messages, exposing authentication credentials in plaintext log files.

MitigationUpgrade Logstash to version 5.6.15, 6.6.1, or later to patch the vulnerable logging behavior. Audit existing log files for exposed credentials and rotate any compromised credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LogstashApplication
Affected:< 5.6.15>= 6.0.0, < 6.6.1
Active Iq Performance Analytics ServicesApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Logstash installation and version
    Run 'bin/logstash --version' (Linux/Unix) or check the installed package version via package manager (e.g., 'rpm -q logstash' or 'dpkg -l logstash'). Alternatively, inspect the VERSION file in the Logstash installation directory.
    Affected if The installed version is less than 5.6.15, or between 6.0.0 and 6.6.0 (inclusive).
  2. Locate Logstash configuration files
    Search for .conf files in the Logstash conf.d directory (commonly /etc/logstash/conf.d/ or /usr/share/logstash/pipeline/) and any referenced configuration paths from the main logstash.yml file.
    Affected if Configuration files exist and contain URL patterns with embedded credentials in the format https://username:password@hostname.
  3. Search logs for exposed credentials
    Examine Logstash logs (typically in /var/log/logstash/ or /usr/share/logstash/logs/) for error messages containing URLs with visible username:password segments. Use grep to search for patterns like 'http://' or 'https://' followed by credentials in log files.
    Affected if Log files contain plaintext credentials embedded in URLs, indicating the vulnerability has been triggered.

You are affected if Logstash version is below 5.6.15 or between 6.0.0 and 6.6.0, AND configuration files contain URLs with embedded credentials that may be logged.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.6.15 / 6.6.1 or later
Fixed in 5.6.156.6.1
Interim mitigation

Upgrade Logstash to version 5.6.15, 6.6.1, or later to patch the vulnerable logging behavior. Audit existing log files for exposed credentials and rotate any compromised credentials.

Recommended fix High confidence

Logstash 5.6.15 (for 5.x branch) or Logstash 6.6.1 (or latest 6.x, for 6.x branch)

  1. 1. Identify the current Logstash version by running: bin/logstash --version (or check the installed package)
  2. 2. Determine the appropriate upgrade path based on your current version branch (5.x or 6.x)
  3. 3. Review the Elastic Stack Upgrade Guide at https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html for your specific upgrade scenario
  4. 4. Create a backup of your Logstash configuration files (usually in /etc/logstash/conf.d/) and any custom plugins
  5. 5. Stop the Logstash service: sudo systemctl stop logstash (or the equivalent for your setup)
  6. 6. Upgrade Logstash using your package manager (apt/yum) to version 5.6.15 (for 5.x users) or 6.6.1 (for 6.x users), or to the latest compatible 6.x release
  7. 7. Verify the new version is installed: bin/logstash --version
  8. 8. Start Logstash and verify normal operation
Caveat Review the Elastic Stack 5.6.15 and 6.6.1 release notes for any breaking changes; major version upgrades (e.g., 5.x to 6.x) may require configuration updates or reindexing of data

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Logstash Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7612 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data