Microsoft Exchange 5.5 SP4
Microsoft Exchange 5.5 SP4
The Microsoft Exchange 5.5 SP4 reached end of service life on Jan 10, 2006 — Microsoft no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Microsoft Exchange 5.5 SP4 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- msexchange
- release
- 5.5
- product Label
- Microsoft Exchange
- release Label
- 5.5 SP4
- codename
- lts
- latest Version
- 5.5.2653
- release Date
- 1998-02-03
- maintained
- source Url
- https://endoflife.date/msexchange
Lifecycle Dates
- End of Service Life
- Jan 10, 2006
- Last OEM Support
- Dec 31, 2003
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Microsoft Exchange 5.5 SP4 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Microsoft Exchange 5.5 SP4?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Microsoft Exchange 5.5 SP4 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Microsoft Exchange 5.5 SP4 Support: Frequently Asked Questions
Is the Microsoft Exchange 5.5 SP4 still supported?
Microsoft ended support for the Microsoft Exchange 5.5 SP4 on Jan 10, 2006 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Microsoft Exchange 5.5 SP4 end of service life (EOSL) date?
Microsoft lists the end of service life for the Microsoft Exchange 5.5 SP4 as Jan 10, 2006.
Can I keep using the Microsoft Exchange 5.5 SP4 after its EOSL date?
Yes. EOSL means Microsoft stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Microsoft Exchange 5.5 SP4 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Microsoft Exchange 5.5 SP4
23 published CVEs affect the Microsoft Exchange 5.5 SP4, including 8 rated critical or high severity. Microsoft no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-1999-0385 | HIGH | 10.0 | Dec 1, 1998 | The LDAP bind function in Exchange 5.5 has a buffer overflow that allows a remote attacker to conduct a denial of service or execute commands. |
| CVE-2006-0002 | HIGH | 7.5 | Jan 10, 2006 | Unspecified vulnerability in Microsoft Outlook 2000 through 2003, Exchange 5.0 Server SP2 and 5.5 SP4, Exchange 2000 SP3, and Office allows remote attackers to execute arbitrary code via an e-mail message with a crafted Transport Neutral Encapsulation Format (TNEF) MIME attachment, related to message length validation. |
| CVE-2003-0714 | HIGH | 7.5 | Nov 17, 2003 | The Internet Mail Service in Exchange Server 5.5 and Exchange 2000 allows remote attackers to cause a denial of service (memory exhaustion) by directly connecting to the SMTP service and sending a certain extended verb request, possibly triggering a buffer overflow in Exchange 2000. |
| CVE-2002-0698 | HIGH | 7.5 | Aug 12, 2002 | Buffer overflow in Internet Mail Connector (IMC) for Microsoft Exchange Server 5.5 allows remote attackers to execute arbitrary code via an EHLO request from a system with a long name as obtained through a reverse DNS lookup, which triggers the overflow in IMC's hello response. |
| CVE-2002-0054 | HIGH | 7.5 | Mar 8, 2002 | SMTP service in (1) Microsoft Windows 2000 and (2) Internet Mail Connector (IMC) in Exchange Server 5.5 does not properly handle responses to NTLM authentication, which allows remote attackers to perform mail relaying via an SMTP AUTH command using null session credentials. |
| CVE-2001-0726 | HIGH | 7.5 | Dec 6, 2001 | Outlook Web Access (OWA) in Microsoft Exchange 5.5 Server, when used with Internet Explorer, does not properly detect certain inline script, which can allow remote attackers to perform arbitrary actions on a user's Exchange mailbox via an HTML e-mail message. |
| CVE-2001-0340 | HIGH | 7.5 | Jul 21, 2001 | An interaction between the Outlook Web Access (OWA) service in Microsoft Exchange 2000 Server and Internet Explorer allows attackers to execute malicious script code against a user's mailbox via a message attachment that contains HTML code, which is executed automatically. |
| CVE-1999-0993 | HIGH | 7.5 | Dec 13, 1999 | Modifications to ACLs (Access Control Lists) in Microsoft Exchange 5.5 do not take effect until the directory store cache is refreshed. |
| CVE-2002-1790 | MEDIUM | 5.0 | Dec 31, 2002 | The SMTP service in Microsoft Internet Information Services (IIS) 4.0 and 5.0 allows remote attackers to bypass anti-relaying rules and send spam or spoofed messages via encapsulated SMTP addresses, a similar vulnerability to CVE-1999-0682. |
| CVE-2001-0660 | MEDIUM | 5.0 | Oct 30, 2001 | Outlook Web Access (OWA) in Microsoft Exchange 5.5, SP4 and earlier, allows remote attackers to identify valid user email addresses by directly accessing a back-end function that processes the global address list (GAL). |
| CVE-2001-0509 | MEDIUM | 5.0 | Sep 20, 2001 | Vulnerabilities in RPC servers in (1) Microsoft Exchange Server 2000 and earlier, (2) Microsoft SQL Server 2000 and earlier, (3) Windows NT 4.0, and (4) Windows 2000 allow remote attackers to cause a denial of service via malformed inputs. |
| CVE-2001-1319 | MEDIUM | 5.0 | Jul 16, 2001 | Microsoft Exchange 5.5 2000 allows remote attackers to cause a denial of service (hang) via exceptional BER encodings for the LDAP filter type field, as demonstrated by the PROTOS LDAPv3 test suite. |
| CVE-1999-0945 | MEDIUM | 5.0 | Mar 12, 2001 | Buffer overflow in Internet Mail Service (IMS) for Microsoft Exchange 5.5 and 5.0 allows remote attackers to conduct a denial of service via AUTH or AUTHINFO commands. |
| CVE-2000-1006 | MEDIUM | 5.0 | Dec 11, 2000 | Microsoft Exchange Server 5.5 does not properly handle a MIME header with a blank charset specified, which allows remote attackers to cause a denial of service via a charset="" command, aka the "Malformed MIME Header" vulnerability. |
| CVE-2000-0216 | MEDIUM | 5.0 | Feb 29, 2000 | Microsoft email clients in Outlook, Exchange, and Windows Messaging automatically respond to Read Receipt and Delivery Receipt tags, which could allow an attacker to flood a mail system with responses by forging a Read Receipt request that is redirected to a large distribution list. |
| CVE-1999-1043 | MEDIUM | 5.0 | Dec 31, 1999 | Microsoft Exchange Server 5.5 and 5.0 does not properly handle (1) malformed NNTP data, or (2) malformed SMTP data, which allows remote attackers to cause a denial of service (application error). |
| CVE-1999-0682 | MEDIUM | 5.0 | Aug 6, 1999 | Microsoft Exchange 5.5 allows a remote attacker to relay email (i.e. spam) using encapsulated SMTP addresses, even if the anti-relaying features are enabled. |
| CVE-1999-0007 | MEDIUM | 5.0 | Jun 26, 1998 | Information from SSL-encrypted sessions via PKCS #1. |
| CVE-1999-1322 | MEDIUM | 4.6 | Nov 12, 1998 | The installation of 1ArcServe Backup and Inoculan AV client modules for Exchange create a log file, exchverify.log, which contains usernames and passwords in plaintext. |
| CVE-2005-0563 | MEDIUM | 4.3 | Jun 14, 2005 | Cross-site scripting (XSS) vulnerability in Microsoft Outlook Web Access (OWA) component in Exchange Server 5.5 allows remote attackers to inject arbitrary web script or HTML via an email message with an encoded javascript: URL ("javAsc
ript:") in an IMG tag. |
Showing the 20 most severe of 23 known CVEs.
Get Third Party Support