CVE-1999-1097
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 · uneditedMicrosoft NetMeeting 2.1 allows one client to read the contents of another client's clipboard via a CTRL-C in the chat box when the box is empty.
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 confidenceMicrosoft NetMeeting 2.1 contains a clipboard information disclosure vulnerability where one client can read the contents of another client's clipboard by pressing CTRL-C in the chat box when the box is empty. This allows unauthorized cross-client clipboard content access.
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<= 2.1CVSS 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
- None
AV:N/AC:L/Au:N/C:P/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.
-
Detect if Microsoft NetMeeting is installedSearch for NetMeeting executable files (such as nm.exe) in typical installation directories like Program Files, or check the Windows Add/Remove Programs list for NetMeeting entriesAffected if Microsoft NetMeeting is found installed on the system
-
Identify the installed NetMeeting versionRight-click the NetMeeting executable, select Properties, and view the Version tab, or launch NetMeeting and check Help > About for the version numberAffected if The version is 2.1 or earlier (any version <= 2.1)
-
Confirm NetMeeting remote call capability is enabledLaunch NetMeeting, go to Tools > Options > Security (or similar legacy UI path), and check whether incoming calls or remote desktop sharing is enabledAffected if NetMeeting is configured to accept incoming calls or has remote data sharing enabled
-
Check for evidence of NetMeeting usage or configurationExamine the NetMeeting configuration files or registry keys under HKLM\Software\Microsoft\NetMeeting for saved settings, or check for recent usage timestamps on NetMeeting executablesAffected if NetMeeting shows recent usage timestamps or contains saved configurations indicating active use
A system is affected if Microsoft NetMeeting version 2.1 or earlier is installed and configured to accept remote connections or has had its chat/clipboard sharing features enabled.
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 dataSince NetMeeting 2.1 is a 1999-era application likely end-of-life, the primary mitigation is to identify and decommission any systems running this legacy software and migrate to current, supported video conferencing solutions.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1097 — 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-1097 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