CommunicatorApplication · Netscape

CVE-1999-1357

HIGH · 7.5 CVSS v2.0 Published 1999-10-05
Fix available
A fix is available. Upgrade to after 4.7 or later.
See remediation →
84/100
Remediation priority · High
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
Netscape Communicator 4.04 through 4.7 (and possibly other versions) in various UNIX operating systems converts the 0x8b character to a "<" sign, and the 0x9b character to a ">" sign, which could allow remote attackers to attack other clients via cross-site scripting (CSS) in CGI programs that do not filter these characters.

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

Netscape Communicator 4.04-4.7 on UNIX converts the hex characters 0x8b to '<' and 0x9b to '>', allowing remote attackers to inject script via CGI programs that fail to filter these specific characters. This is a client-side cross-site scripting (XSS) vulnerability in the browser itself, where the conversion enables attack payloads that would otherwise be filtered by servers expecting standard angle brackets.

MitigationThis vulnerability affects only obsolete Netscape Communicator 4.x browsers from 1999-2001; modern browsers do not exhibit this character conversion behavior. Organizations should ensure legacy systems are upgraded or decommissioned, and web applications should implement standard input validation regardless.

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
CommunicatorApplication
Affected:<= 4.7= 4.04= 4.51

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
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 checks

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

  1. Identify installed browser software
    Check what web browser is installed on the UNIX system by examining installed packages, application directories, or running 'ls' on common Netscape installation paths such as /usr/local/netscape or ~/.netscape
    Affected if The installed browser is anything other than Netscape Communicator for UNIX
  2. Determine Netscape Communicator version
    Run the Netscape browser with version flags such as 'netscape -version' or 'netscape -about', or check the application binary and installation metadata for the exact version number
    Affected if The version is not 4.04, 4.51, or any version between 4.05 and 4.7 inclusive
  3. Confirm operating system is UNIX
    Check the operating system using commands like 'uname -a', 'uname -s', or examining /etc/os-release to verify the system is a UNIX variant (Solaris, AIX, HP-UX, Linux, etc.)
    Affected if The operating system is not a UNIX variant (this vulnerability is specific to UNIX versions of Netscape Communicator)
  4. Verify the vulnerable character conversion behavior
    Create a test HTML page containing the hex characters 0x8b and 0x9b (encoded as \x8b and \x9b) and open it in the affected Netscape Communicator version to confirm these are rendered as '<' and '>' respectively
    Affected if The browser renders 0x8b as '<' or 0x9b as '>' (this conversion is the core vulnerability mechanism)

A system is affected if it runs Netscape Communicator version 4.04, 4.51, or any version between 4.05 and 4.7 on a UNIX operating system, and the browser exhibits the hex character to angle bracket conversion behavior.

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.

From vendor data
Upgrade available Upgrade to a release after 4.7
Interim mitigation

This vulnerability affects only obsolete Netscape Communicator 4.x browsers from 1999-2001; modern browsers do not exhibit this character conversion behavior. Organizations should ensure legacy systems are upgraded or decommissioned, and web applications should implement standard input validation regardless.

Fix this in Communicator Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-1357 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-1999-1357 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