CVE-1999-0332
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 · uneditedBuffer overflow in NetMeeting allows denial of service and remote command execution.
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 confidenceA buffer overflow vulnerability in Microsoft NetMeeting, a legacy video conferencing application, allows remote attackers to cause denial of service or potentially execute arbitrary code via crafted network requests.
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
- 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.
-
Check if NetMeeting is installedNavigate to Control Panel > Programs and Features, or check for the presence of NetMeeting executable files (nm.exe or conf.exe) in system directories such as C:\Program Files\NetMeeting or C:\Windows\System32Affected if NetMeeting application is found installed on the system
-
Identify the installed versionRight-click on the NetMeeting executable (nm.exe) and select Properties, then check the Details tab for version information, or launch NetMeeting and go to Help > AboutAffected if The installed version is exactly 2.1
-
Verify if NetMeeting process is runningOpen Task Manager and look for nm.exe or conf.exe processes, or run 'tasklist /FI "IMAGENAME eq nm.exe"' from command promptAffected if NetMeeting process is actively running on the system
-
Confirm if remote access is enabledCheck NetMeeting settings under Tools > Options > General tab for 'Enable remote desktop sharing' or 'Accept calls', or examine Windows Firewall rules for exceptions related to NetMeeting (ports 1503, 389, 522, 1720)Affected if NetMeeting is configured to accept incoming network requests or calls
The system is affected if Microsoft NetMeeting version 2.1 is installed and configured to accept remote connections, as the buffer overflow can be exploited via crafted network requests to this service.
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 is deprecated and no longer receives security updates, organizations should uninstall or disable the application immediately. Network-based controls like firewalls and segmentation can provide additional protection where removal isn't feasible.
- 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-0332 — 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-0332 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