dbcve.org
Ip600 Media ServersApplication · Avaya

CVE-2004-0212

HIGH · 10.0 CVSS v2.0 Published 2004-08-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click Patch available

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 · unedited
Stack-based buffer overflow in the Task Scheduler for Windows 2000 and XP, and Internet Explorer 6 on Windows NT 4.0, allows local or remote attackers to execute arbitrary code via a .job file containing long parameters, as demonstrated using Internet Explorer and accessing a .job file on an anonymous share.

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

A detailed technical summary for this CVE is being prepared.

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
Ip600 Media ServersApplication
Affected:all versions
IeApplication
Affected:= 6.0
Definity One Media ServerHardware / appliance
Affected:all versions
S8100Hardware / appliance
Affected:all versions
Modular Messaging Message Storage ServerOperating system
Affected:= s3400
Windows 2000Operating system
Affected:all versions
Windows NtOperating system
Affected:= 4.0
Windows XpOperating system
Affected:all versions

CVSS 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

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.us-cert.gov →
Recommended fix High confidence

Windows 10 or Windows 11 (or Windows Server 2016/2019/2022 for server environments)

  1. 1. Identify all systems running the affected Windows versions (Windows 2000, Windows XP, Windows NT 4.0) that use Task Scheduler
  2. 2. Check if the system still has Microsoft support and can receive security updates
  3. 3. If the system is still under support, apply Microsoft Security Bulletin MS04-022 (the vendor patch for this vulnerability)
  4. 4. If the system is end-of-life (no longer supported), plan for migration to a supported Windows version such as Windows 10 or Windows 11
  5. 5. As a temporary mitigation, disable Task Scheduler service or restrict access to .job file handling until the system can be upgraded
  6. 6. Ensure Internet Explorer 6 is not used or is properly sandboxed/disabled on affected systems
  7. 7. Implement network segmentation to limit exposure if immediate upgrade is not possible
Caveat These legacy systems (Windows 2000, XP, NT 4.0) are end-of-life and may have application compatibility issues when migrating to modern Windows; plan for application testing and potential updates

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0212 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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