# CVE-2019-18850: Information disclosure in n/a

> TrevorC2 allows fingerprinting via response header discrepancies and predictable responses, exposing server details to attackers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xmvf-mpjx-5xvj

## What is CVE-2019-18850?

CVE-2019-18850 is a high-severity vulnerability in n/a, published on 4 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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".

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2019-18850?

It affects 1 product.


Products: Trustedsec Trevorc2.

## How do I fix CVE-2019-18850?

No fix has been published for CVE-2019-18850 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-18850 being exploited?

There is no known exploitation of CVE-2019-18850 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18850 and fix it if it is affected.

What it is: CVE-2019-18850 is a high-severity vulnerability in n/a, published on 4 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18850 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18850/ (Markdown: https://insights.sbomify.com/CVE-2019-18850/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18850
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18850
- OSV: https://osv.dev/vulnerability/CVE-2019-18850

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18850/
Summaries are generated and may contain mistakes; the official description above is the record.