CVE-2000-0383
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 · uneditedThe file transfer component of AOL Instant Messenger (AIM) reveals the physical path of the transferred file to the remote recipient.
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 confidenceAOL Instant Messenger's file transfer functionality inadvertently discloses the local physical file path (e.g., C:\Users\John\Documents\file.exe) to the recipient during file transfer negotiations, revealing potentially sensitive directory structure information.
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.0CVSS 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.
-
Verify AIM installationSearch for 'aim.exe' in common installation directories such as C:\Program Files\AOL Instant Messenger or C:\Program Files (x86)\AOL Instant Messenger. Also check Start Menu shortcuts and Add/Remove Programs for AOL Instant Messenger entry.Affected if AOL Instant Messenger version 4.0 is installed on the system
-
Confirm AIM version numberRight-click on the AIM executable or shortcut, select Properties, and examine the Version tab. Alternatively, right-click in the AIM window, select 'About AOL Instant Messenger' to display the version information.Affected if The displayed version is exactly 4.0
-
Check for recent AIM file transfer activityReview recent file transfers sent or received through AIM. Examine AIM log files in the installation directory or user profile folder for records of file transfer events.Affected if File transfers have been performed using AIM 4.0
-
Inspect file transfer configurationIn AIM 4.0, go to Edit > Settings > File Transfer to examine the file transfer settings. Verify whether the file transfer feature is enabled and review any configurable options.Affected if File transfer functionality is enabled in AIM 4.0
The system is affected if AOL Instant Messenger version 4.0 is installed and the file transfer feature has been used to send or receive files, as the local physical file path would be disclosed to the transfer recipient.
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 AIM for file transfers; employ alternative secure file sharing methods (encrypted email attachments, secure file transfer protocols, or reputable cloud storage services).
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0383 — 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-0383 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