Salt 3005
Salt 3005
The Salt 3005 reached end of service life on Feb 25, 2024 — Salt 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 Salt 3005 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
- salt
- release
- 3005
- product Label
- Salt
- release Label
- 3005
- codename
- lts
- latest Version
- 3005.5
- release Date
- 2022-08-22
- maintained
- source Url
- https://endoflife.date/salt
Lifecycle Dates
- End of Service Life
- Feb 25, 2024
- Last OEM Support
- Aug 25, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Salt 3005 — 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 Salt 3005?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Salt 3005 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.
Salt 3005 Support: Frequently Asked Questions
Is the Salt 3005 still supported?
Salt ended support for the Salt 3005 on Feb 25, 2024 — 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 Salt 3005 end of service life (EOSL) date?
Salt lists the end of service life for the Salt 3005 as Feb 25, 2024.
Can I keep using the Salt 3005 after its EOSL date?
Yes. EOSL means Salt 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 Salt 3005 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 Salt 3005
2 published CVEs affect the Salt 3005. Salt no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-20897 | MEDIUM | 5.3 | Sep 5, 2023 | Salt masters prior to 3005.2 or 3006.2 contain a DOS in minion return. After receiving several bad packets on the request server equal to the number of worker threads, the master will become unresponsive to return requests until restarted. |
| CVE-2023-20898 | MEDIUM | 4.2 | Sep 5, 2023 | Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash. |