CVE-2019-18187
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 versions 11.0 and XG (12.0) could be exploited by an attacker utilizing a directory traversal vulnerability to extract files from an arbitrary zip file to a specific folder on the OfficeScan server, which could potentially lead to remote code execution (RCE). The remote process execution is bound to a web service account, which depending on the web platform used may have restricted permissions. An attempted attack requires user authentication.
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 confidenceA directory traversal vulnerability in Trend Micro OfficeScan versions 11.0 and XG (12.0) allows authenticated attackers to extract files from arbitrary zip archives to specific folders on the server, potentially achieving remote code execution though constrained by the web service account permissions.
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= xgCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 OfficeScan versionAccess the OfficeScan management console or check the product itself to determine the exact version number. Look for version 11.0 or XG (also labeled as version 12.0).Affected if The installed version is exactly 11.0 or XG (12.0)
-
Verify authenticated access existsConfirm that valid credentials exist for the OfficeScan web management console. The vulnerability requires an authenticated attacker to exploit the zip extraction functionality.Affected if Valid administrator or operator credentials can be used to log into the OfficeScan web console
-
Locate zip upload functionalityIn the OfficeScan management console, navigate to sections that handle file uploads, archives, or pattern updates where zip file extraction may occur. Look for features that accept and extract zip files.Affected if The zip file extraction feature is accessible via the web interface
-
Inspect web service accountCheck the account context under which the OfficeScan web service runs. This is typically found in Windows Services or the server's service configuration.Affected if The web service runs with elevated privileges that could allow file writes outside the intended directory
-
Monitor for suspicious file creationReview server filesystem for any files created outside the expected OfficeScan directories, particularly in system directories or web root locations. Look for unexpected .exe, .dll, or script files.Affected if Files exist in locations outside the normal OfficeScan installation directory, especially with path traversal patterns (e.g., ../../)
A user is affected if their OfficeScan installation is version 11.0 or XG (12.0) and the zip file extraction feature is accessible to authenticated users, allowing potential path traversal file writes.
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 dataApply vendor-supplied patches for OfficeScan 11.0 and XG (12.0); if patches are unavailable, restrict administrative access to the management interface and minimize network exposure to prevent authenticated exploitation.
- 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-2019-18187 — 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-18187 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