CVE-2017-8801
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 · uneditedTrend Micro OfficeScan 11.0 before SP1 CP 6325 (with Agent Module Build before 6152) and XG before CP 1352 has XSS via a crafted URI using a blocked website.
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 confidenceCross-site scripting (XSS) vulnerability in Trend Micro OfficeScan 11.0 and XG web interface. The flaw allows injection of malicious scripts through crafted URIs when handling blocked website requests, potentially enabling session hijacking or credential theft via user browser execution.
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= 11.0= 12.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 OfficeScan installationLocate the OfficeScan installation directory (typically C:\Program Files\Trend Micro\OfficeScan or similar) or check Programs and Features for Trend Micro OfficeScan. On Windows, use reg query 'HKLM\SOFTWARE\TrendMicro\OfficeScan' /v InstallPath if installed.Affected if OfficeScan is not installed or the installation path cannot be found.
-
Determine OfficeScan versionCheck the installed version - for 11.0, look in the web console under Help > About, or check the registry key HKLM\SOFTWARE\TrendMicro\OfficeScan\CurrentVersion or examine the version info of the main executable (e.g., TmListen.exe, PccNTMon.exe) in the installation folder.Affected if The installed version is exactly 11.0 or exactly 12.0.
-
Confirm web interface is enabledAccess the OfficeScan web console URL (typically https://localhost:4343/officescan or the configured server URL). Verify the web management console is accessible and not disabled via registry key HKLM\SOFTWARE\TrendMicro\OfficeScan\setup\bWebConsoleEnabled set to 0, or check that the IIS/Apache service hosting the console is running.Affected if The web interface is enabled and accessible (default state for most installations).
-
Check web proxy functionalityIn the OfficeScan web console, navigate to Web Reputation > Settings or Proxy settings. Verify if the web proxy/blocked request handling feature is configured. From command line, check registry HKLM\SOFTWARE\TrendMicro\OfficeScan\plugin\WRS for enabled status.Affected if Web Reputation or web proxy functionality is enabled, which allows the server to handle blocked website requests.
If OfficeScan 11.0 or 12.0 is installed with the web interface and web proxy/reputation feature enabled, the environment is vulnerable to XSS via crafted URIs in blocked website request handling.
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 dataUpgrade to OfficeScan 11.0 SP1 CP 6325 or later (Agent Module Build 6152+) or XG CP 1352 or later. If immediate upgrade is not feasible, restrict web proxy functionality and implement input validation at upstream proxies.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8801 — 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-8801 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