CVE-2019-7617 json
Elastic APM agent for Python client CGI proxy redirection flaw
published 7y ago modified 4mo ago also GHSA-22jh-6gx8-f944 , PYSEC-2019-178 , EUVD-2019-0048
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
When the Elastic APM agent for Python versions before 5.1.0 is run as a CGI script, there is a variable name clash flaw if a remote attacker can control the proxy header. This could result in an attacker redirecting collected APM data to a proxy of their choosing.
Patch / fix
- pypi elastic-apm 5.1.0
- elastic apm_agent 5.1.0
Is CVE-2019-7617 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
| GitHub | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | elastic-apm | <5.1.0 |
5.1.0 |
Affected products
- Elastic Elastic APM agent for Python
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
elastic.co
/community/security/
vendor-advisory, web
-
discuss.elastic.co
/t/elastic-apm-agent-for-python-5-1-0-security-update/196145
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-7617
advisory
-
github.com
/elastic/apm-agent-python
package
-
github.com
/pypa/advisory-database/tree/main/vulns/elastic-apm/PYSEC-2019-178.yaml
web
-
elastic.co
/community/security
web
-
github.com
/advisories/GHSA-22jh-6gx8-f944
advisory
Sources
- CVE List CVE-2019-7617
- GitHub Advisory GHSA-22jh-6gx8-f944
- NVD CVE-2019-7617
- OSV PYSEC-2019-178
Fencer Intel 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.