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

> Attackers can detect Canarytokens in Word documents due to predictable metadata, bypassing the deception mechanism.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 14 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3gff-8v36-4xj9

## What is CVE-2019-9768?

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

### Official description

Thinkst Canarytokens through commit hash 4e89ee0 (2019-03-01) relies on limited variation in size, metadata, and timestamp, which makes it easier for attackers to estimate whether a Word document contains a token.

Weakness: CWE-264

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

It affects 1 product.


Products: Thinkst Canarytokens.

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

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

## Is CVE-2019-9768 being exploited?

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

Public exploit code:

- Canarytokens 2019-03-01 - Detection Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-28111](https://insights.sbomify.com/CVE-2024-28111/): CSV Injection in exported history CSV files (medium 6.5)
- [CVE-2023-22475](https://insights.sbomify.com/CVE-2023-22475/): Cross-Site Scripting in Canarytoken history (medium 6.3)
- [CVE-2022-31113](https://insights.sbomify.com/CVE-2022-31113/): Cross-Site Scripting in Canarytoken history (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9768 is a high-severity vulnerability in n/a, published on 14 Mar 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-9768 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-9768/ (Markdown: https://insights.sbomify.com/CVE-2019-9768/index.md)
```

## Sources

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

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