HTTP ServerWeb server / proxy · Apache
CVE-1999-1237
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 · uneditedMultiple buffer overflows in smbvalid/smbval SMB authentication library, as used in Apache::AuthenSmb and possibly other modules, allows remote attackers to execute arbitrary commands via (1) a long username, (2) a long password, and (3) other unspecified methods.
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 confidenceMultiple buffer overflow vulnerabilities in the smbvalid/smbval SMB authentication library (used by Apache::AuthenSmb and potentially other modules) allow remote attackers to execute arbitrary commands via overly long username, password, or other unspecified vectors in the SMB authentication process.
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
HTTP ServerWeb server / proxy
all versionsCVSS 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 for smbvalid/smbval library presenceSearch the system for files named smbval.c, smbval.h, libsmbval.so, or smbval.o in common library and source directories (e.g., /usr/lib, /usr/local/lib, /usr/include, /opt)Affected if The smbvalid/smbval library files are present on the system
-
Check for Apache::AuthenSmb Perl moduleRun 'perl -MApache::AuthenSmb -e 1' or check for AuthenSmb.pm in Perl library paths (perl -V shows @INC)Affected if The Apache::AuthenSmb Perl module is installed
-
Inspect Apache configuration for AuthenSmb usageSearch Apache config files (httpd.conf, apache2.conf, included .conf files) for directives 'PerlAuthenHandler Apache::AuthenSmb' or references to AuthenSmbAffected if Apache is configured to use Apache::AuthenSmb for authentication
-
Check for SMB authentication configurationLook in Apache config for directives specifying SMB authentication such as 'AuthenSmbType', 'AuthenSmbRealm', or smbval-related settingsAffected if Apache is configured to authenticate against an SMB server using smbval
A system is affected if the smbvalid/smbval library and Apache::AuthenSmb module are installed and actively configured for Apache authentication, regardless of Apache version.
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 dataReplace the deprecated smbvalid/smbval library and Apache::AuthenSmb with modern authentication mechanisms (e.g., LDAP, PAM, or OAuth); if continued SMB authentication is required, implement strict input length validation and consider upgrading to current, actively-maintained alternatives.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1237 — 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-1237 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