diff --git a/docs/advisories/20240911002-Ivanti-Publishes-Critical-Security-Updates.md b/docs/advisories/20240911002-Ivanti-Publishes-Critical-Security-Updates.md new file mode 100644 index 00000000..bf160d53 --- /dev/null +++ b/docs/advisories/20240911002-Ivanti-Publishes-Critical-Security-Updates.md @@ -0,0 +1,31 @@ +# 20240911002 - Ivanti Publishes Critical Security Updates + +## Overview + +Ivanti has released updates for Ivanti Endpoint Manager 2024 and 2022 SU6 which addresses medium and high vulnerabilities. Successful exploitation could lead to unauthorized access to the EPM core server. + +## What is vulnerable? + +| **Product(s) Affected** | **Version(s)** | **CVE#** | **CVSS v4/v3** | **Severity** | +|---------------------------|----------------------------|--------------------------------------------------------------------|----------------|--------------| +| Ivanti EPM | 2024, 2022 SU5 and earlier | [CVE-2024-32840](https://nvd.nist.gov/vuln/detail/CVE-2024-32840) | 9.1 | Critical | +| | | [CVE-2024-32842](https://nvd.nist.gov/vuln/detail/CVE-2024-32842) | 9.1 | Critical | +| | | [CVE-2024-32843](https://nvd.nist.gov/vuln/detail/CVE-2024-32843) | 9.1 | Critical | +| | | [CVE-2024-32845](https://nvd.nist.gov/vuln/detail/CVE-2024-32845) | 9.1 | Critical | +| | | [CVE-2024-32846](https://nvd.nist.gov/vuln/detail/CVE-2024-32846) | 9.1 | Critical | +| | | [CVE-2024-32848](https://nvd.nist.gov/vuln/detail/CVE-2024-32848) | 9.1 | Critical | +| | | [CVE-2024-34779](https://nvd.nist.gov/vuln/detail/CVE-2024-34779) | 9.1 | Critical | +| | | [CVE-2024-34783](https://nvd.nist.gov/vuln/detail/CVE-2024-34783) | 9.1 | Critical | +| | | [CVE-2024-34785](https://nvd.nist.gov/vuln/detail/CVE-2024-34785) | 9.1 | Critical | +| | | [CVE-2024-29847](https://nvd.nist.gov/vuln/detail/CVE-2024-29847) | 10 | Critical | + +## What has been observed? + +There is no evidence of exploitation affecting Western Australian Government networks at the time of publishing. + +## Recommendation + +The WA SOC recommends administrators apply the solutions as per vendor instructions to all affected devices within expected timeframe of *48 hours...* (refer [Patch Management](../guidelines/patch-management.md)): + +- +