UnrealIRCd 3.2
UnrealIRCd 3.2
The UnrealIRCd 3.2 reached end of service life on Dec 31, 2016 — UnrealIRCd 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 UnrealIRCd 3.2 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
- unrealircd
- release
- 3.2
- product Label
- UnrealIRCd
- release Label
- 3.2
- codename
- lts
- latest Version
- 3.2.10.7
- release Date
- 2004-04-25
- maintained
- source Url
- https://endoflife.date/unrealircd
Lifecycle Dates
- End of Service Life
- Dec 31, 2016
- Last OEM Support
- Dec 11, 2015
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for UnrealIRCd 3.2 — 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 UnrealIRCd 3.2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for UnrealIRCd 3.2 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.
UnrealIRCd 3.2 Support: Frequently Asked Questions
Is the UnrealIRCd 3.2 still supported?
UnrealIRCd ended support for the UnrealIRCd 3.2 on Dec 31, 2016 — 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 UnrealIRCd 3.2 end of service life (EOSL) date?
UnrealIRCd lists the end of service life for the UnrealIRCd 3.2 as Dec 31, 2016.
Can I keep using the UnrealIRCd 3.2 after its EOSL date?
Yes. EOSL means UnrealIRCd 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 UnrealIRCd 3.2 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 UnrealIRCd 3.2
6 published CVEs affect the UnrealIRCd 3.2, including 2 rated critical or high severity. UnrealIRCd no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2016-7144 | HIGH | 8.1 | Jan 18, 2017 | The m_authenticate function in modules/m_sasl.c in UnrealIRCd before 3.2.10.7 and 4.x before 4.0.6 allows remote attackers to spoof certificate fingerprints and consequently log in as another user via a crafted AUTHENTICATE parameter. |
| CVE-2010-2075 | HIGH | 7.5 | Jun 15, 2010 | UnrealIRCd 3.2.8.1, as distributed on certain mirror sites from November 2009 through June 2010, contains an externally introduced modification (Trojan Horse) in the DEBUG3_DOLOG_SYSTEM macro, which allows remote attackers to execute arbitrary commands. |
| CVE-2009-4893 | MEDIUM | 6.8 | Jun 15, 2010 | Buffer overflow in UnrealIRCd 3.2beta11 through 3.2.8, when allow::options::noident is enabled, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors. |
| CVE-2017-13649 | MEDIUM | 5.5 | Aug 23, 2017 | UnrealIRCd 4.0.13 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill `cat /pathname`" command. NOTE: the vendor indicates that there is no common or recommended scenario in which a root script would execute this kill command. |
| CVE-2013-7384 | MEDIUM | 5.0 | May 19, 2014 | UnrealIRCd 3.2.10 before 3.2.10.2 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via unspecified vectors, related to SSL. NOTE: this issue was SPLIT from CVE-2013-6413 per ADT2 due to different vulnerability types. |
| CVE-2013-6413 | MEDIUM | 5.0 | May 19, 2014 | Use-after-free vulnerability in UnrealIRCd 3.2.10 before 3.2.10.2 allows remote attackers to cause a denial of service (crash) via unspecified vectors. NOTE: this identifier was SPLIT per ADT2 due to different vulnerability types. CVE-2013-7384 was assigned for the NULL pointer dereference. |