Endpoint AntivirusApplication · Eset
CVE-2023-5594
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 · uneditedImproper validation of the server’s certificate chain in secure traffic scanning feature considered intermediate certificate signed using the MD5 or SHA1 algorithm as trusted.
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 confidenceThe secure traffic scanning feature improperly validates certificate chains by trusting intermediate certificates signed with weak hash algorithms (MD5 or SHA1). These algorithms are cryptographically broken and allow attackers to forge certificates, enabling man-in-the-middle attacks on SSL/TLS traffic being scanned.
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
Endpoint AntivirusApplication
>= 10.0all versions
Server SecurityApplication
>= 10.1all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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.
-
Identify installed ESET product and versionOpen Programs and Features (appwiz.cpl) or check C:\Program Files\ESET for the installed product folder. Right-click the ESET icon in the system tray and select About to view the exact version number.Affected if The product is one of: ESET Endpoint Antivirus (version 10.0+), ESET Server Security (version 10.1+), ESET Endpoint Security, ESET File Security, ESET Internet Security, ESET Mail Security, ESET NOD32 Antivirus, or ESET Security.
-
Confirm the secure traffic scanning feature is enabledOpen the ESET main interface. Navigate to Setup > Network protection or Settings > Network. Look for options labeled 'Secure traffic scanning', 'SSL/TLS scanning', 'Protected traffic scanning', or similar. Verify the feature is turned ON or Enabled.Affected if The secure traffic scanning or SSL/TLS inspection feature is actively enabled, allowing ESET to intercept and scan encrypted traffic.
-
Verify certificate chain validation settingsIn the ESET network protection settings, locate the certificate validation or SSL/TLS inspection configuration section. Look for options controlling which hash algorithms are accepted for intermediate certificate validation.Affected if The configuration allows or does not explicitly block MD5 or SHA1 hash algorithms for intermediate certificate chain validation.
You are affected if you have any ESET product from the affected list with secure traffic scanning enabled, and certificate chain validation does not explicitly reject weak hash algorithms (MD5/SHA1) for intermediate certificates.
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.
From vendor dataUpdate the certificate chain validation logic in the secure traffic scanning feature to reject intermediate certificates signed with MD5 or SHA1 algorithms, requiring at minimum SHA-256 or stronger for trusted certificate chains.
Fix this in Endpoint Antivirus
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5594 — 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-2023-5594 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