CVE-2019-7615 json
Elastic APM agent for Ruby vulnerable to Improper Certificate Validation
published 2019-07-30 7 y ago modified 2026-06-17 4 mo ago also GHSA-35j2-p8fh-x966 , EUVD-2022-2113
- cvss
- 7.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rubygems elastic-apm 2.9.0
- elastic apm-agent-ruby 2.9.0
- github.com/elastic/apm-agent-ruby#449 pull request
Exploit prediction
0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | elastic-apm | <2.9.0 |
2.9.0 |
Affected products
- Elastic Elastic APM agent for Ruby
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
github.com
/elastic/apm-agent-ruby/pull/449
web
-
elastic.co
/community/security/
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-7615
advisory
-
github.com
/elastic/apm-agent-ruby
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/elastic-apm/CVE-2019-7615.yml
web
-
elastic.co
/community/security
web
Sources
- CVE List CVE-2019-7615
- GitHub Advisory GHSA-35j2-p8fh-x966
- NVD CVE-2019-7615
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.