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

> Attackers can intercept or modify data transmitted over raw sockets in UCI IDOL 2 due to lack of authentication and endpoint verification.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-wcph-x6mx-4gh6

## What is CVE-2024-45168?

CVE-2024-45168 is a critical missing authorization vulnerability in n/a, published on 22 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in UCI IDOL 2 (aka uciIDOL or IDOL2) through 2.12. Data is transferred over a raw socket without any authentication mechanism. Thus, communication endpoints are not verifiable.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Uci Idol2.

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

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

## Is CVE-2024-45168 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45168 exists.

## Other vulnerabilities in n/a

- [CVE-2024-45166](https://insights.sbomify.com/CVE-2024-45166/): Deserialization in n/a (critical 9.8)
- [CVE-2024-45167](https://insights.sbomify.com/CVE-2024-45167/): Denial of service in n/a (critical 9.8)
- [CVE-2024-45169](https://insights.sbomify.com/CVE-2024-45169/): Deserialization in n/a (critical 9.8)
- [CVE-2024-45165](https://insights.sbomify.com/CVE-2024-45165/): Hardcoded credentials in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45168 is a critical missing authorization vulnerability in n/a, published on 22 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45168 exists.

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-45168/ (Markdown: https://insights.sbomify.com/CVE-2024-45168/index.md)
```

## Sources

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

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