CVE-1999-0182
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 · uneditedSamba has a buffer overflow which allows a remote attacker to obtain root access by specifying a long password.
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 confidenceSamba versions prior to patches contained a buffer overflow vulnerability in password handling logic. By sending a specially long password field, a remote unauthenticated attacker could overflow a stack buffer and execute arbitrary code with root privileges on the affected system.
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<= 1.9.17CVSS 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.
-
Check if Samba is installedRun command: rpm -qa | grep -i samba (RHEL/CentOS), dpkg -l | grep -i samba (Debian), or which smbd nmbdAffected if No Samba packages or binaries found means not affected
-
Determine installed Samba versionRun command: smbd --version or rpm -q samba or dpkg -s sambaAffected if Version is 1.9.17 or lower, or version cannot be determined (indicating very old install)
-
Check if SMB services are runningRun command: ps aux | grep -E 'smbd|nmbd' or systemctl status smb nmbAffected if smbd or nmbd processes are running - the vulnerable password handling code is active
-
Verify SMB ports are listeningRun command: netstat -tlnp | grep -E ':139|:445' or ss -tlnp | grep -E ':139|:445'Affected if Ports 139 or 445 are open and accepting connections - the attack surface is exposed
System is affected if Samba version 1.9.17 or lower is installed AND SMB services (smbd/nmbd) are running and accessible on network ports.
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.
dbcve · scopedUpgrade to a patched version of Samba or migrate to a currently supported Samba release. If immediate patching is not feasible, restrict network access to SMB services (ports 445/139) via firewall to prevent external exploitation.
Samba 4.x (modern stable release, e.g., 4.18.x or latest 4.x)
- Identify all systems running Samba version 1.9.17 or earlier
- Stop the Samba service on affected systems
- Backup all Samba configuration files (smb.conf) and user databases
- Uninstall the old Samba version
- Install a current stable Samba version (Samba 4.x series)
- Restore the backed-up configuration files
- Verify the configuration syntax with 'testparm'
- Start the Samba service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0182 — 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-0182 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