CVE-2017-18227
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 · uneditedTitanHQ WebTitan Gateway has incorrect certificate validation for the TLS interception feature.
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 · moderate confidenceTitanHQ WebTitan Gateway contains improper certificate validation in its TLS interception feature. This allows the gateway to accept invalid, expired, or maliciously crafted certificates during TLS inspection, potentially enabling man-in-the-middle attacks or bypassing TLS security controls.
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 dataall 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm WebTitan Gateway is installedLocate the WebTitan Gateway installation directory or check running services for 'webtitan' or 'wtg' processesAffected if WebTitan Gateway software is present on the system
-
Identify if TLS interception is enabledAccess the WebTitan Gateway admin console and navigate to TLS/SSL inspection settings, or check configuration files for 'tls_inspection', 'ssl_interception', or 'MITM' settingsAffected if TLS interception/SSL inspection feature is turned on
-
Verify hostname verification is configuredCheck TLS interception settings for 'hostname verification', 'server name indication (SNI) validation', or 'CN matching' configuration optionsAffected if Hostname verification is disabled or not enforced in TLS interception settings
-
Check trust chain validation settingsInspect TLS interception configuration for 'trust chain validation', 'CA certificate validation', or 'certificate chain verification' optionsAffected if Trust chain validation is disabled or bypassed for intercepted connections
-
Verify revocation checking statusLook for 'OCSP', 'CRL', or 'certificate revocation' settings within the TLS interception moduleAffected if Certificate revocation checking is disabled or not configured
User is affected if WebTitan Gateway is installed with TLS interception feature enabled and any certificate validation controls (hostname verification, trust chain, revocation) are disabled or misconfigured
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 dataEnsure proper certificate chain validation including hostname verification, trust chain validation, and revocation checking in the TLS interception module. Consider disabling TLS interception until a patch is applied if the risk is unacceptable.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18227 — 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-2017-18227 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