CVE-2019-8351
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHeimdal Thor Agent 2.5.17x before 2.5.173 does not verify X.509 certificates from TLS servers, which allows remote attackers to spoof servers and obtain sensitive information via a crafted certificate.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHeimdal Thor Agent versions 2.5.17x through 2.5.172 fail to validate X.509 certificates during TLS server connections, allowing man-in-the-middle attackers to spoof legitimate servers using crafted certificates and intercept sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.5.170= 2.5.171= 2.5.172CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Thor Agent installationCheck if Heimdal Security Thor is installed on the system using standard software inventory tools or package managersAffected if Thor Agent is not installed on the system
-
Determine installed Thor Agent versionUse system tools to retrieve the installed version of Thor Agent (e.g., program files listing, software inventory, or version information in the application itself)Affected if Unable to determine the version number from the installation
-
Compare version against affected releasesVerify if the installed version matches exactly 2.5.170, 2.5.171, or 2.5.172Affected if The installed version is exactly 2.5.170, 2.5.171, or 2.5.172
-
Confirm TLS connectivity is in useObserve whether Thor Agent establishes TLS connections to remote servers (the vulnerability affects TLS server certificate validation during these connections)Affected if Thor Agent uses TLS connections and the version is in the affected range
A system is affected if Heimdal Security Thor Agent version 2.5.170, 2.5.171, or 2.5.172 is installed and actively using TLS connections to communicate with servers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Thor Agent to version 2.5.173 or later which implements proper X.509 certificate chain validation and hostname verification.
Thor 2.5.173 or later
- 1. Navigate to the Heimdal Security support portal at support.heimdalsecurity.com
- 2. Locate the download section for Thor Agent
- 3. Download version 2.5.173 or later
- 4. Run the installer with administrative privileges
- 5. Follow the on-screen prompts to complete the upgrade
- 6. Verify the installed version matches 2.5.173 or newer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8351 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data