CVE-2002-0697
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 Metadirectory Services (MMS) 2.2 allows remote attackers to bypass authentication and modify sensitive data by using an LDAP client to directly connect to MMS and bypass the checks for MMS credentials.
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 confidenceMicrosoft Metadirectory Services (MMS) 2.2 contains an authentication bypass vulnerability where remote attackers can use a direct LDAP client connection to bypass MMS credential checks and modify sensitive directory data without proper authentication.
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.2CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Confirm MMS 2.2 installationCheck running services or installed programs for Microsoft Metadirectory Services version 2.2. On Windows, examine Add/Remove Programs or the services list for 'Microsoft Metadirectory Services' or 'MMS' entry showing version 2.2.Affected if Microsoft Metadirectory Services version 2.2 is installed and running on the system
-
Verify LDAP service availabilityCheck if the LDAP service (typically port 389 or 636 for SSL) is listening on the server where MMS is installed. Use netstat or port scanning tools to enumerate open LDAP ports.Affected if LDAP ports are open and listening on the MMS server
-
Assess LDAP direct connection exposureDetermine if external or unauthorized LDAP client connections are permitted to the MMS server. Review network firewall rules, LDAP bind settings, and access control lists that govern who can initiate direct LDAP connections to the directory.Affected if The LDAP service is network-accessible without proper network segmentation or access restrictions
-
Check LDAP authentication configurationReview the MMS LDAP configuration to determine whether it permits anonymous binds or allows direct connections that bypass MMS credential verification mechanisms.Affected if LDAP configuration allows unauthenticated or credential-checking-bypassing connections
The environment is affected if Microsoft Metadirectory Services 2.2 is installed with an exposed LDAP service that permits direct connections without proper MMS credential validation.
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 MMS 2.2 is a legacy product from 2002 likely beyond mainstream support, the primary remediation is to decommission or replace with a supported directory services solution; alternatively, implement network segmentation and LDAP access controls to restrict unauthorized direct connections.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0697 — 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-0697 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