dbcve.org
Apm Agent RubyApplication · Elastic

CVE-2019-7615

HIGH · 7.4 CVSS v3.1 Published 2019-07-30
Fix available
A fix is available. Upgrade to 2.9.0 or later.
See remediation →
83/100
Remediation priority · High
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 TLS certificate validation flaw was found in Elastic APM agent for Ruby versions before 2.9.0. When specifying a trusted server CA certificate via the 'server_ca_cert' setting, the Ruby agent would not properly verify the certificate returned by the APM server. This could result in a man in the middle style attack against the Ruby agent.

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

The Elastic APM agent for Ruby versions before 2.9.0 contains a TLS certificate validation flaw where the 'server_ca_cert' setting is not properly verifying the certificate returned by the APM server, enabling man-in-the-middle attacks.

MitigationUpgrade the elastic-apm Ruby gem to version 2.9.0 or later to resolve the certificate validation failure.

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
Apm Agent RubyApplication
Affected:< 2.9.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 if Elastic APM Ruby agent is in use
    Check Gemfile or gem list for the 'elastic-apm' gem. Run 'gem list elastic-apm' or inspect the project's Gemfile
    Affected if The elastic-apm gem is present in the environment
  2. Check installed elastic-apm gem version
    Run 'gem list elastic-apm' or 'gem info elastic-apm' to see the installed version number
    Affected if The version displayed is less than 2.9.0 (e.g., 2.8.x, 2.7.x, etc.)
  3. Locate APM agent configuration
    Look for configuration file: config/elastic_apm.yml, or environment variables starting with 'ELASTIC_APM_', or inline config in the application code where ElasticAPM.start is called
    Affected if A configuration file or environment variables for Elastic APM exist
  4. Check if server_ca_cert is configured
    Inspect the configuration file or environment variables for the 'server_ca_cert' setting. Search for 'server_ca_cert' or 'SSL_CERT_FILE' / 'ELASTIC_APM_SERVER_CA_CERT' in the config
    Affected if The server_ca_cert option is present and set to a certificate file path or inline certificate

User is affected if the elastic-apm gem version is below 2.9.0 AND the server_ca_cert setting is configured in their APM agent configuration.

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.

From vendor data
Upgrade available Upgrade to 2.9.0 or later
Fixed in 2.9.0
Interim mitigation

Upgrade the elastic-apm Ruby gem to version 2.9.0 or later to resolve the certificate validation failure.

Fix this in Apm Agent Ruby Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7615 — 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-7615 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