CVE-2000-0034
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 · uneditedNetscape 4.7 records user passwords in the preferences.js file during an IMAP or POP session, even if the user has not enabled "remember passwords."
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 confidenceNetscape Communicator 4.7 stores user IMAP and POP3 passwords in plaintext within the preferences.js file located in the user's profile directory, even when the 'remember passwords' feature is explicitly disabled. This creates a local information disclosure vulnerability where any user or process with filesystem access to the profile can retrieve stored credentials.
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= 4.7CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Verify Netscape Communicator 4.7 is installedCheck the program files directory for Netscape\Communicator folder or check registry for Netscape installation entries. Look for netscape.exe version 4.7 or check Add/Remove Programs for Netscape Communicator 4.7.Affected if Netscape Communicator version 4.7 is found on the system
-
Locate the user profile directoryNavigate to the typical profile location: on Windows this is typically C:\Windows\Profiles\username\Application Data\Netscape\Users\username or C:\Documents and Settings\username\Application Data\Netscape\Users\usernameAffected if A Netscape profile directory exists for the user
-
Find and inspect the preferences.js fileOpen the preferences.js file located in the profile directory using a text editor or command: type "preferences.js" or cat preferences.jsAffected if The preferences.js file exists in the profile directory
-
Search for plaintext IMAP or POP3 password stringsSearch within preferences.js for patterns like "IMAPPassword" or "POP3Password" followed by readable text strings. Use findstr /C:"IMAPPassword" /C:"POP3Password" preferences.jsAffected if Plaintext strings resembling IMAP or POP3 passwords are present in the file, even with 'remember passwords' disabled
If Netscape Communicator 4.7 is installed and its preferences.js file in the user profile contains plaintext IMAP or POP3 password entries, the system is affected by CVE-2000-0034.
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 dataDiscontinue use of Netscape 4.7 and migrate to modern mail clients; if legacy systems must operate, restrict filesystem access to profile directories and audit for exposed credential files.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0034 — 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-0034 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