CVE-1999-0537
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 configuration in a web browser such as Internet Explorer or Netscape Navigator allows execution of active content such as ActiveX, Java, Javascript, etc.
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 confidenceThis vulnerability describes web browsers (Internet Explorer, Netscape Navigator) configured to allow execution of active content such as ActiveX, Java, and JavaScript. This configuration permits potentially malicious code to run on the client system, leading to remote code execution, data theft, or system compromise.
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= 6.0.2900all 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify installed Internet Explorer versionOpen Command Prompt and run: reg query 'HKLM\SOFTWARE\Microsoft\Internet Explorer' /v VersionAffected if version equals 6.0.2900 (IE6) and ActiveX, Java, or JavaScript execution is enabled in security settings
-
Identify installed Netscape Communicator versionLaunch Netscape and check Help > About Netscape Navigator, or check the executable version property in File ExplorerAffected if any Netscape Communicator version is installed and active content execution is permitted
-
Check Internet Explorer ActiveX controls settingsOpen IE > Tools > Internet Options > Security > Custom Level. Look for 'Run ActiveX controls and plugins' setting under the ActiveX controls and plugins sectionAffected if ActiveX controls are set to Enable or Prompt (not Disabled)
-
Check Internet Explorer Java permissionsOpen IE > Tools > Internet Options > Security > Custom Level. Look for 'Java permissions' under the Microsoft VM sectionAffected if Java permissions are set to High Safety, Medium Safety, or Low Safety (not Disable)
-
Check browser JavaScript execution setting (IE)Open IE > Tools > Internet Options > Security > Custom Level. Look for 'Active scripting' under the Scripting sectionAffected if Active scripting is set to Enable or Prompt (not Disabled)
-
Check Netscape JavaScript execution settingIn Netscape Navigator, type 'about:config' in the address bar. Look for 'javascript.enabled' preferenceAffected if javascript.enabled is set to true (enabled)
A user is affected if they run Internet Explorer 6.0.2900 or any Netscape Communicator version AND have ActiveX, Java, or JavaScript execution enabled in their browser security settings.
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 dataDisable or restrict execution of ActiveX, Java, and JavaScript in browser security settings; deploy browser hardening policies; use modern browsers with built-in security controls and automatic updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0537 — 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-1999-0537 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