# CVE-2020-1887: Weak cryptography in Osquery

> Attackers can intercept osquery traffic via MITM due to improper TLS SNI validation when no root chain of trust is configured.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 12 Mar 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-1887?

CVE-2020-1887 is a critical vulnerability in Facebook Osquery, published on 12 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect validation of the TLS SNI hostname in osquery versions after 2.9.0 and before 4.2.0 could allow an attacker to MITM osquery traffic in the absence of a configured root chain of trust.

Weakness: CWE-295 (Improper Certificate Validation), CWE-297 (Improper Validation of Certificate with Host Mismatch)

## Which versions are affected by CVE-2020-1887?

It affects 1 product.


Products: Linuxfoundation Osquery.

## How do I fix CVE-2020-1887?

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

## Is CVE-2020-1887 being exploited?

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

## Other vulnerabilities in Facebook Osquery

- [CVE-2019-3567](https://insights.sbomify.com/CVE-2019-3567/): Path traversal in osquery (high 8.1)
- [CVE-2018-6336](https://insights.sbomify.com/CVE-2018-6336/): Security feature bypass in osquery (high 7.8)
- [CVE-2020-11081](https://insights.sbomify.com/CVE-2020-11081/): osquery susceptible to DLL search order hijacking of zlib1.dll (medium 5.3)
- [CVE-2020-26273](https://insights.sbomify.com/CVE-2020-26273/): sqlite ATTACH allows some filesystem access (medium 5.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1887 and fix it if it is affected.

What it is: CVE-2020-1887 is a critical vulnerability in Facebook Osquery, published on 12 Mar 2020. 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-2020-1887 in the wild and no public exploit code.

Affected product: Facebook Osquery. 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-2020-1887/ (Markdown: https://insights.sbomify.com/CVE-2020-1887/index.md)
```

## Sources

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

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