CVE-2007-0655
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 · uneditedThe MicroWorld Agent service (MWAGENT.EXE) in MicroWorld Technologies eScan 8.0.671.1, and possibly other versions, allows remote or local attackers to gain privileges and execute arbitrary commands by connecting directly 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 confidenceThe MicroWorld Agent service (MWAGENT.EXE) in eScan antivirus listens on TCP port 2222 and allows unauthenticated remote or local attackers to execute arbitrary commands with elevated privileges by directly connecting to this port.
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<= 8.0671.1CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if eScan antivirus is installedLook for eScan installation directory (typically C:\Program Files\eScan or C:\Program Files (x86)\eScan) or check Add/Remove Programs for Microworld eScan entryAffected if eScan antivirus is present on the system
-
Verify MWAGENT.EXE service is runningOpen Task Manager or run 'tasklist /FI "IMAGENAME eq MWAGENT.EXE"' in command prompt to check if the service process is activeAffected if MWAGENT.EXE process is running on the system
-
Confirm TCP port 2222 is listeningRun 'netstat -an | findstr :2222' or use PowerShell 'Get-NetTCPConnection -LocalPort 2222' to check if the service port is open and accepting connectionsAffected if TCP port 2222 is in LISTENING state and reachable
-
Determine installed eScan versionCheck version information in Add/Remove Programs, or look for version file in eScan installation directory, or right-click MWAGENT.EXE and select Properties > DetailsAffected if Installed version is 8.0671.1 or earlier (any version <= 8.0671.1)
The system is affected if eScan antivirus is installed with version <= 8.0671.1, the MWAGENT.EXE service is running, and TCP port 2222 is open and listening.
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 dataRestrict network access to TCP port 2222 via firewall rules, or disable the MWAGENT service if not required for business operations. If the software is still in use, contact vendor for patched version.
- Consultation4.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0655 — 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-2007-0655 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