CVE-2019-9768: High severity thinkst vulnerability

Published Mar 14, 2019
·
Updated

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.

Affected Software

1 affected component
Thinkst Canarytokens<=2019-03-01

Event History

Mar 14, 2019
CVE Published
via MITRE·07:00 AM
Data Sourced
via MITRE·07:00 AM
Description
Data Sourced
via NVD·09:29 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-9768?

CVE-2019-9768 has a medium severity level due to its potential for information disclosure and token detection by attackers.

2

How do I fix CVE-2019-9768?

To mitigate CVE-2019-9768, upgrade to a version of Thinkst Canarytokens released after March 1, 2019.

3

What types of tokens are affected by CVE-2019-9768?

CVE-2019-9768 affects Word document tokens that rely on specific size and metadata characteristics.

4

Who is affected by CVE-2019-9768?

Any users running affected versions of Thinkst Canarytokens prior to version 2019-03-01 are vulnerable to CVE-2019-9768.

5

What is the impact of exploiting CVE-2019-9768?

Exploiting CVE-2019-9768 allows attackers to more easily identify and bypass Canarytokens within Word documents.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203