CVE-2000-0119
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 default configurations for McAfee Virus Scan and Norton Anti-Virus virus checkers do not check files in the RECYCLED folder that is used by the Windows Recycle Bin utility, which allows attackers to store malicious code without detection.
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 confidenceMcAfee Virus Scan and Norton Anti-Virus default configurations do not scan the Windows RECYCLED folder, which is where deleted files are stored in the Recycle Bin. This allows malicious code to be placed in the Recycle Bin without detection by the antivirus software.
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 dataall versionsall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Confirm antivirus product installationCheck system for McAfee Virus Scan or Norton AntiVirus installation by reviewing installed programs or running 'wmic product get name' in command promptAffected if Either McAfee Virus Scan or Norton AntiVirus is installed
-
Identify default scan configurationOpen the antivirus software and navigate to the default or custom scan settings. Look for options related to scanning hidden folders, system folders, or specific directoriesAffected if Scan settings are at default configuration and do not explicitly include the RECYCLED folder in the scan path
-
Check for RECYCLED folder exclusion or omissionIn the antivirus scan configuration, locate the folder/directory exclusions or include lists. Verify whether the RECYCLED folder is listed or excluded from scanningAffected if The RECYCLED folder is not included in the active scan paths or is explicitly excluded from scans
-
Verify scan target settingsReview the antivirus scan profile or task settings to see which folders are targeted for scanning, particularly looking for settings related to scanning deleted file locationsAffected if The scan configuration does not cover the Recycle Bin directory (RECYCLED folder) in its default or active scan scope
If McAfee Virus Scan or Norton AntiVirus is installed with default scan settings that do not include the RECYCLED folder, the environment is affected by this vulnerability.
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 dataConfigure antivirus software to scan all directories including hidden and system folders like RECYCLED, or ensure the antivirus definitions and product versions include the RECYCLED folder in default scans.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0119 — 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-2000-0119 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