# CVE-2024-4465: Incorrect authorization for Reports configuration in Guardian/CMC before 24.2.0

> A logged-in user with reporting privileges can modify report configurations, potentially causing data integrity loss, DoS, or credential exposure via SMTP redirection.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2024
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-vr5r-frmj-8fwp

## What is CVE-2024-4465?

CVE-2024-4465 is a medium-severity missing authorization vulnerability in Nozomi Networks CMC, published on 11 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An access control vulnerability was discovered in the Reports section due to a specific access restriction not being properly enforced for users with limited privileges.

If a logged-in user with reporting privileges learns how to create a specific application request, they might be able to make limited changes to the reporting configuration. This could result in a partial loss of data integrity. In Guardian/CMC instances with a reporting configuration, there could be limited Denial of Service (DoS) impacts, as the reports may not reach their intended destination, and there could also be limited information disclosure impacts. Furthermore, modifying the destination SMTP server for the reports could lead to the compromise of external credentials, as they might be sent to an unauthorized server. This could expand the scope of the attack.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-4465?

It affects 2 products.


Products: Nozominetworks Cmc, Nozominetworks Guardian.

## How do I fix CVE-2024-4465?

No fix has been published for CVE-2024-4465 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4465 being exploited?

There is no known exploitation of CVE-2024-4465 in the wild and no public exploit code.

## Other vulnerabilities in Nozomi Networks CMC

- [CVE-2023-29245](https://insights.sbomify.com/CVE-2023-29245/): SQL Injection on IDS parsing of malformed asset fields in Guardian/CMC >= 22.6.0 before 22.6.3 and 23.1.0 (critical 9.2)
- [CVE-2026-31984](https://insights.sbomify.com/CVE-2026-31984/): DoS through oversized audit log entries in Guardian/CMC before 26.2.0 (high 8.7)
- [CVE-2023-2567](https://insights.sbomify.com/CVE-2023-2567/): Authenticated SQL Injection on Query functionality in Guardian/CMC before 22.6.3 and 23.1.0 (high 8.7)
- [CVE-2023-22378](https://insights.sbomify.com/CVE-2023-22378/): Authenticated Blind SQL Injection on sorting in Guardian/CMC before 22.6.2 (high 8.7)
- [CVE-2023-23574](https://insights.sbomify.com/CVE-2023-23574/): Authenticated Blind SQL Injection on alerts count in Guardian/CMC before 22.6.2 (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4465 and fix it if it is affected.

What it is: CVE-2024-4465 is a medium-severity missing authorization vulnerability in Nozomi Networks CMC, published on 11 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4465 in the wild and no public exploit code.

Affected product: Nozomi Networks CMC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4465/ (Markdown: https://insights.sbomify.com/CVE-2024-4465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4465
- OSV: https://osv.dev/vulnerability/CVE-2024-4465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4465/
Summaries are generated and may contain mistakes; the official description above is the record.