dbcve.org
Ip600 Media ServersApplication · Avaya

CVE-2004-1050

HIGH · 10.0 CVSS v2.0 Published 2004-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

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
Heap-based buffer overflow in Internet Explorer 6 allows remote attackers to execute arbitrary code via long (1) SRC or (2) NAME attributes in IFRAME, FRAME, and EMBED elements, as originally discovered using the mangleme utility, aka "the IFRAME vulnerability" or the "HTML Elements Vulnerability."

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 confidence

Heap-based buffer overflow in Internet Explorer 6 triggered by excessively long SRC or NAME attributes in IFRAME, FRAME, and EMBED HTML elements. The vulnerability allows remote attackers to execute arbitrary code by overflowing the heap via these attribute values.

MitigationUpgrade from Internet Explorer 6 to a currently supported browser (IE 11, Edge, Chrome, Firefox) or apply Microsoft security patches if continued IE6 use is absolutely required.

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
Ip600 Media ServersApplication
Affected:all versions= r6= r7= r8= r9= r10= r11= r12
IeApplication
Affected:= 6.0
Internet ExplorerApplication
Affected:= 6.0
Definity One Media ServerHardware / appliance
Affected:all versions= r6= r7= r8= r9= r10= r11= r12
S3400Hardware / appliance
Affected:all versions
S8100Hardware / appliance
Affected:all versions= r6= r7= r8= r9= r10= r11= r12
Modular Messaging Message Storage ServerOperating system
Affected:= s3400

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Internet Explorer version
    Open Internet Explorer, click Help > About Internet Explorer, or run 'winver' command to see installed Windows/IE version. Alternatively, check the file version of iexplore.exe at C:\Program Files\Internet Explorer\iexplore.exe or C:\Program Files (x86)\Internet Explorer\iexplore.exe
    Affected if The installed version is exactly Internet Explorer 6.0
  2. Check for IE6 in Avaya Ip600 Media Server
    Verify if the Avaya Ip600 Media Server software is installed. Check program files for Avaya directories or look for Avaya Ip600 components in Add/Remove Programs
    Affected if The Avaya Ip600 Media Server (any version r6-r12 or all versions) is installed and bundled with IE6
  3. Check for IE6 in Avaya Definity One Media Server
    Verify if the Avaya Definity One Media Server software is installed. Check for Avaya Definity One installation directories or registry entries
    Affected if The Avaya Definity One Media Server (any version r6-r12 or all versions) is installed and uses IE6
  4. Check for IE6 in Avaya S3400 or S8100
    Verify if Avaya S3400 or S8100 systems are installed. Check for Avaya installation directories or running services related to these products
    Affected if Avaya S3400 (all versions) or Avaya S8100 (any version r6-r12 or all versions) is installed and incorporates IE6 components
  5. Check for IE6 in Avaya Modular Messaging Message Storage Server
    Verify if the Avaya Modular Messaging Message Storage Server (s3400 variant) is installed
    Affected if The Avaya Modular Messaging Message Storage Server version s3400 is installed and includes IE6

You are affected if Internet Explorer 6.0 is installed directly or is bundled with any Avaya product (Ip600, Definity One, S3400, S8100, or Modular Messaging) listed in the affected versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from Internet Explorer 6 to a currently supported browser (IE 11, Edge, Chrome, Firefox) or apply Microsoft security patches if continued IE6 use is absolutely required.

Recommended fix High confidence

Internet Explorer 8 or later / Microsoft Edge / Modern browsers (Chrome, Firefox)

  1. 1. Identify all systems running Internet Explorer 6.0 in the environment
  2. 2. Upgrade Internet Explorer 6.0 to Internet Explorer 8 (the last supported version for Windows XP) or migrate to Microsoft Edge on supported Windows versions
  3. 3. For Windows XP systems (which only support up to IE8), consider upgrading the operating system to a supported version to access newer browsers
  4. 4. Alternatively, deploy modern browsers such as Google Chrome, Mozilla Firefox, or Microsoft Edge as primary browsers
  5. 5. Verify that all browsers are updated to their latest stable versions
  6. 6. Test critical web applications for compatibility with newer browser versions
  7. 7. Remove or disable Internet Explorer 6.0 from all systems if not required for legacy application support
Caveat Legacy web applications designed specifically for IE6 may not function properly in newer browsers; may require application remediation or legacy browser support

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

Fix this in Ip600 Media Servers Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-1050 — 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-1050 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