CVE-2002-1695
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 · uneditedNorton Internet Security 2001 opens log files with FILE_SHARE_READ and FILE_SHARE_WRITE permissions, which could allow remote attackers to modify the log file contents while Norton Internet Security is running.
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 confidenceNorton Internet Security 2001 opens log files with both FILE_SHARE_READ and FILE_SHARE_WRITE permissions, which allows an attacker with local or remote system access to modify log file contents while the application is running. This could enable log injection, log corruption, or exploitation of log-parsing vulnerabilities.
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.0= 5.0= 2001CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Identify if Norton Internet Security 2001 is installedCheck the installed programs list in Windows Control Panel, or look for Norton Internet Security installation directories (typically in Program Files\Norton Internet Security or Program Files\Symantec\Norton Internet Security)Affected if Norton Internet Security version 2001 is present on the system
-
Confirm the exact version numberRight-click on the Norton Internet Security executable or DLL file, select Properties, and check the Version tab. Alternatively, run 'msiexec /x {productcode}' or check Add/Remove Programs for the specific version string.Affected if The installed version is Norton Internet Security 2001 (any sub-version)
-
Determine if logging is enabledOpen Norton Internet Security 2001, navigate to Options or Settings, and look for logging-related settings (often under Security, Firewall, or Logs). Check if logging to file is turned on.Affected if File-based logging is enabled and log files are being written to disk
-
Inspect log file sharing permissionsUse Sysinternals Process Monitor or check the file properties of active Norton log files (typically in the Norton program folder or Windows System32\LogFiles). Right-click the log file, go to Properties, then Security to see if the file is open with shared write access.Affected if Log files exist and are actively being written to by the application
If Norton Internet Security 2001 is installed with file-based logging enabled, the system is vulnerable to log file manipulation due to the overly permissive file sharing flags.
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 dataNorton Internet Security 2001 is a discontinued end-of-life product. Upgrade to a currently supported Norton security product. If legacy use is unavoidable, implement strict file system access controls on log directories to prevent unauthorized modification.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1695 — 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-2002-1695 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