CVE-1999-1012
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 · uneditedSMTP component of Lotus Domino 4.6.1 on AS/400, and possibly other operating systems, allows a remote attacker to crash the mail server via a long string.
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 confidenceDenial of service vulnerability in Lotus Domino 4.6.1 SMTP component on AS/400 and possibly other platforms. A remote attacker can crash the mail server by sending an excessively long string to the SMTP service.
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.6.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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Verify Lotus Domino installationCheck for Lotus Domino installation by looking for Domino program files, typically in C:\Lotus\Domino (Windows) or /opt/lotus/domino (Unix/Linux), or query the system for installed software named 'Lotus Domino'Affected if Lotus Domino is not installed on the system
-
Confirm installed Domino versionRun the Domino console command 'show version' or check the program files for a version file. On Windows, right-click the Domino executable and select Properties > Version tab. On AS/400, use the WRKOBJ command to check Domino objects.Affected if The installed version is exactly 4.6.1
-
Check if SMTP service is enabledIn Domino Administrator, go to Server > Status and verify if SMTP is listed as running. Alternatively, check the notes.ini file for 'SMTPServer=1' or review the Server Document in the Domino Directory under Programming > SMTP.Affected if SMTP service is enabled and listening on port 25
-
Identify SMTP listening interfacesReview the Server Document in the Domino Directory under Ports > Internet Ports. Check if SMTP is bound to all interfaces (0.0.0.0) or specific IP addresses, and verify network exposure.Affected if SMTP is accessible from network interfaces beyond localhost
The environment is affected only if Lotus Domino version 4.6.1 is installed AND the SMTP service is enabled and exposed.
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 dataUpgrade from Lotus Domino 4.6.1 to a supported, patched version. If the legacy system cannot be upgraded immediately, consider network segmentation or firewall rules to restrict SMTP access to trusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1012 — 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-1012 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