Security readout for executives and security teams
Plain-English summary
A very old flaw in Slmail version 2.5 lets a remote attacker crash the mail server's POP3 mailbox service, blocking users from retrieving email until the service is restarted. The public record from 1999 is thin on details, and Slmail 2.5 is long out of support, so the practical concern today is only for organizations still running this legacy software.
Executive priority
Low priority for modern environments. Only material if legacy Slmail v2.5 is still deployed; in that case, prioritize decommissioning the unsupported mail server rather than patching this specific bug.
Technical view
CVE-1999-0272 describes a denial-of-service condition in Seattle Lab Mail (Slmail) v2.5 reachable through the POP3 service (typically TCP/110). Public sources do not specify the exact trigger, CWE, or CVSS. No vendor patch is cited in the bundle. The record is a legacy MITRE entry with an IBM X-Force cross-reference and no KEV listing.
Likely exposure
Extremely narrow. Slmail 2.5 is a 1990s Windows mail product; modern enterprises are unlikely to run it. Exposure exists only where a legacy Slmail POP3 listener remains reachable, typically on internal networks or forgotten hosts.
Exploitation context
Not listed in CISA KEV. The cited sources do not document active exploitation or public exploit availability tied to this CVE ID. Any attacker impact is limited to disrupting POP3 mail retrieval on the affected legacy server, not code execution per the public description.
Researcher notes
Sparse legacy entry: no CWE, CVSS, affected CPE, or exploit reference is provided in the bundle beyond the X-Force cross-link. Treat as denial-of-service against the POP3 listener only; do not assume RCE. Confirm any current attack surface through inventory, not by inferring from the 1999 description.
Mitigation direction
- Inventory hosts for Slmail v2.5 and any legacy Seattle Lab Mail installations.
- Retire or migrate off Slmail; the product is unsupported and lacks a vendor patch path.
- If retention is required, restrict POP3 (TCP/110) access to trusted management networks only.
- Check current vendor or successor guidance before applying any workaround.
- Monitor the POP3 service for repeated crashes and unexpected restarts.
Validation and detection
- Confirm whether any host runs Slmail 2.5 by checking installed software and POP3 service banners.
- Verify reachability of TCP/110 from untrusted networks using authorized network scans.
- Review mail server availability logs for prior POP3 crashes or service restarts.
- Cross-check CVE-1999-0272 against your vulnerability scanner results for legacy detections.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-1999-0272 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0272CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.