# CVE-2024-45164: Missing authorization in n/a

> An authenticated user can bypass authorization controls to disable policy enforcement in Akamai SIA ThreatAvert by accessing a specific URI.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 4 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-xqww-45ww-cw2p

## What is CVE-2024-45164?

CVE-2024-45164 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Akamai SIA (Secure Internet Access Enterprise) ThreatAvert, in SPS (Security and Personalization Services) before the latest 19.2.0 patch and Apps Portal before 19.2.0.3 or 19.2.0.20240814, has incorrect authorization controls for the Admin functionality on the ThreatAvert Policy page. An authenticated user can navigate directly to the /#app/intelligence/threatAvertPolicies URI and disable policy enforcement.

Weakness: CWE-863 (Incorrect Authorization), CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Akamai Secure Internet Access Enterprise Threatavert.

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

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

## Is CVE-2024-45164 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45164 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 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-45164 in the wild and no public exploit code.

Affected product: n/a. 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-45164/ (Markdown: https://insights.sbomify.com/CVE-2024-45164/index.md)
```

## Sources

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

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