Escan Anti VirusApplication · Escanav
CVE-2025-0720
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 · uneditedA vulnerability was found in Microword eScan Antivirus 7.0.32 on Linux. It has been rated as problematic. Affected by this issue is the function removeExtraSlashes of the file /opt/MicroWorld/sbin/rtscanner of the component Folder Watch List Handler. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceStack-based buffer overflow in the removeExtraSlashes function of the rtscanner (real-time scanner) component in eScan Antivirus 7.0.32 on Linux. The function fails to properly validate path length when removing extra slashes from folder paths in the Watch List Handler, allowing a local attacker to overflow a stack buffer and potentially execute arbitrary code.
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
Escan Anti VirusApplication
= 7.0.32CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Confirm eScan Antivirus installation and versionRun 'rpm -qa | grep escan' or 'dpkg -l | grep escan' depending on your package manager, or check for the presence of /opt/escan or /usr/lib/escan directoriesAffected if The installed version is exactly 7.0.32
-
Locate the rtscanner binarySearch for the rtscanner binary using 'find / -name rtscanner 2>/dev/null' or check common eScan installation paths like /opt/escan/Affected if The rtscanner binary exists and is from eScan version 7.0.32
-
Verify the Watch List Handler configurationCheck eScan configuration files for Watch List settings, typically found in /opt/escan/etc/ or /etc/escan/ directoryAffected if A Watch List is configured with folder paths that the rtscanner monitors in real-time
-
Confirm rtscanner service is activeCheck if the rtscanner service is running using 'ps aux | grep rtscanner' or 'systemctl status escan'Affected if The rtscanner service is actively running and processing watched folder paths
You are affected only if eScan Antivirus version 7.0.32 is installed with the rtscanner component active and a Watch List configured, as the buffer overflow occurs in the removeExtraSlashes function when processing watched folder paths.
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 dataSince the vendor did not respond to the disclosure, implement compensating controls: restrict physical and shell access to the system, run the antivirus with minimum privileges, or consider alternative antivirus solutions. Monitor for any publicly available exploits targeting this vulnerability.
Fix this in Escan Anti Virus
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0720 — 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-2025-0720 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