Skip to content
Fencer Intel
medium 5.3

CVE-2024-45431 json

OpenSynergy BlueSDK (aka Blue SDK) through 6.x has Improper Input Validation.

published last yr. modified 15d ago also EUVD-2024-55014

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
5.6%
EPSS 5.6% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

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.

Is CVE-2024-45431 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

5.63% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • pcacybersecurity.com https://pcacybersecurity.com/resources/advisory/perfekt-blue referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.