ArangoDB 3.4
ArangoDB 3.4
The ArangoDB 3.4 reached end of service life on Jun 21, 2020 — ArangoDB 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 ArangoDB 3.4 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
- arangodb
- release
- 3.4
- product Label
- ArangoDB
- release Label
- 3.4
- codename
- lts
- latest Version
- 3.4.11
- release Date
- 2018-12-05
- maintained
- source Url
- https://endoflife.date/arangodb
Lifecycle Dates
- End of Service Life
- Jun 21, 2020
- Last OEM Support
- Jun 21, 2020
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for ArangoDB 3.4 — 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 ArangoDB 3.4?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for ArangoDB 3.4 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.
ArangoDB 3.4 Support: Frequently Asked Questions
Is the ArangoDB 3.4 still supported?
ArangoDB ended support for the ArangoDB 3.4 on Jun 21, 2020 — 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 ArangoDB 3.4 end of service life (EOSL) date?
ArangoDB lists the end of service life for the ArangoDB 3.4 as Jun 21, 2020.
Can I keep using the ArangoDB 3.4 after its EOSL date?
Yes. EOSL means ArangoDB 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 ArangoDB 3.4 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 ArangoDB 3.4
1 published CVE affects the ArangoDB 3.4. ArangoDB no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2021-25938 | MEDIUM | 6.1 | May 24, 2021 | In ArangoDB, versions v2.2.6.2 through v3.7.10 are vulnerable to Cross-Site Scripting (XSS), since there is no validation of the .zip file name and filtering of potential abusive characters which zip files can be named to. There is no X-Frame-Options Header set, which makes it more susceptible for leveraging self XSS by attackers. |