CVE-2009-0802
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 · uneditedQbik WinGate, when transparent interception mode is enabled, uses the HTTP Host header to determine the remote endpoint, which allows remote attackers to bypass access controls for Flash, Java, Silverlight, and probably other technologies, and possibly communicate with restricted intranet sites, via a crafted web page that causes a client to send HTTP requests with a modified Host header.
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 confidenceQbik WinGate proxy in transparent interception mode uses the HTTP Host header to determine the destination endpoint, allowing attackers to craft malicious web pages that modify the Host header to bypass access controls. This enables unauthorized communication with restricted intranet sites through Flash, Java, Silverlight, and other technologies that may not respect proxy settings.
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= 6.0.0= 6.0.1_build_993= 6.0.1_build_995= 6.0.2_build_1000= 6.0.2_build_1001= 6.0.3_build_1005= 6.1= 6.1.1.1077= 6.1.2= 6.1.3= 6.1.4= 6.2CVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:H/Au:N/C:C/I:N/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 if WinGate proxy is installedLocate WinGate installation directory or check for WinGate services running on the system. Common paths may include C:\Program Files\WinGate or similar. Check Windows services for 'WinGate' or 'WingateEngine' services.Affected if WinGate proxy software is found on the system
-
Determine the installed WinGate versionCheck the version information of the WinGate executable or consult the WinGate management interface for the build number. Compare the installed version and build number against the affected list: 6.0.0, 6.0.1_build_993, 6.0.1_build_995, 6.0.2_build_1000, 6.0.2_build_1001, 6.0.3_build_1005, 6.1, 6.1.1.1077, 6.1.2, 6.1.3, 6.1.4, or 6.2.Affected if The installed version matches one of the affected versions listed in the CVE
-
Verify if transparent interception mode is enabledAccess the WinGate management console and inspect the proxy configuration settings. Look for transparent interception or transparent proxy settings in the HTTP proxy configuration section.Affected if Transparent interception mode is enabled in the WinGate proxy configuration
The system is affected if WinGate proxy is installed, the version matches one of the affected builds (6.0.0 through 6.2), and transparent interception mode is currently enabled.
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 dataDisable transparent interception mode if not required, or implement additional validation of the Host header against allowed destinations. Consider upgrading WinGate to a version that addresses this flaw if a patch is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0802 — 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-2009-0802 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