CVE-2019-18850: TrevorC2 v1.1/v1.2 fails to prevent fingerprinting primarily via a discrepancy between response headers when r
CVE-2019-18850 is a high-severity flaw (CVSS 7.5) affecting trevorc2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
TrevorC2 v1.1/v1.2 fails to prevent fingerprinting primarily via a discrepancy between response headers when responding to different HTTP methods, also via predictible responses when accessing and interacting with the "SITE_PATH_QUERY".
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-18850?
trevorc2: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2019-18850 being exploited?
CVE-2019-18850 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-18850 affect?
CVE-2019-18850 affects trevorc2. Severity is high (CVSS 7.5). TrevorC2 v1.1/v1.2 fails to prevent fingerprinting primarily via a discrepancy between response headers when responding to different HTTP methods, also via predictible responses when accessing and interacting with the "SITE_PATH_QUERY".
How urgent is CVE-2019-18850?
Priority 48/100. High severity; Remotely exploitable, no login, no user action