# CVE-2024-45431: Other in n/a

> An attacker can create an L2CAP channel with a null remote CID due to improper input validation in the BlueSDK Bluetooth stack.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 12 Sep 2025
- **Updated:** 12 Sep 2025
- **Also known as:** GHSA-jq7h-rrc8-hx39

## What is CVE-2024-45431?

CVE-2024-45431 is a medium-severity vulnerability in n/a, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSynergy BlueSDK (aka Blue SDK) through 6.x has Improper Input Validation. The specific flaw exists within the BlueSDK Bluetooth stack. The issue results from the lack of proper validation of remote L2CAP channel ID (CID). An attacker can leverage this to create an L2CAP channel with the null identifier assigned as a remote CID.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Opensynergy Blue Sdk.

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

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

## Is CVE-2024-45431 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-45434](https://insights.sbomify.com/CVE-2024-45434/): Use after free in n/a (critical 9.8)
- [CVE-2024-45432](https://insights.sbomify.com/CVE-2024-45432/): Information disclosure in n/a (high 7.5)
- [CVE-2018-20378](https://insights.sbomify.com/CVE-2018-20378/): Memory corruption in n/a (high 7.5)
- [CVE-2024-45433](https://insights.sbomify.com/CVE-2024-45433/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45431 is a medium-severity vulnerability in n/a, published on 12 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45431 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-45431/ (Markdown: https://insights.sbomify.com/CVE-2024-45431/index.md)
```

## Sources

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

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