CVE-2018-18388
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 · uneditedeScan Agent Application (MWAGENT.EXE) 4.0.2.98 in MicroWorld Technologies eScan 14.0 allows remote or local attackers to execute arbitrary commands by sending a carefully crafted payload to TCP port 2222.
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 confidenceCommand injection vulnerability in eScan Agent Application (MWAGENT.EXE) version 4.0.2.98 allows remote or local attackers to execute arbitrary commands by sending a crafted payload to TCP port 2222, which the agent service listens on.
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= 14.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 eScan Anti Virus is installedCheck for eScan Anti Virus installation by looking in Add/Remove Programs (Windows) or checking for eScan installation directories (typically in C:\Program Files\eScan or C:\Program Files (x86)\eScan)Affected if eScan Anti Virus version 14.0 is installed on the system
-
Confirm installed eScan versionOpen the eScan application interface and navigate to About or Help section to view the exact version number, or check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\eScan for DisplayVersionAffected if The installed version is exactly 14.0 (version 14.0.0.0 or similar 14.x releases)
-
Check if MWAGENT.EXE process is runningOpen Task Manager or run 'tasklist | findstr MWAGENT' in command prompt to verify if the eScan Agent Application process (MWAGENT.EXE) is currently activeAffected if MWAGENT.EXE process is running on the system
-
Verify TCP port 2222 is listeningRun 'netstat -ano | findstr :2222' or use PowerShell 'Get-NetTCPConnection -LocalPort 2222' to check if port 2222 is in Listening stateAffected if TCP port 2222 is open and listening, indicating the vulnerable agent service is active
If eScan Anti Virus version 14.0 is installed with MWAGENT.EXE running and listening on TCP port 2222, the environment is affected by CVE-2018-18388 and is vulnerable to command injection attacks via that port.
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 available vendor patches or update to a patched version of eScan. If immediate patching is not feasible, restrict network access to TCP port 2222 through firewalls or network segmentation to limit attack surface.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18388 — 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-2018-18388 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