Connman vulnerabilitiesRanked by how likely they are to be used.

Product127 versions
The short answer

Connman is made by Intel. We track 10 published vulnerabilities in it, across 127 versions. None of them is on the list of flaws known to be exploited today. If you run Connman, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Connman vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Connman's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Connman flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 5.5%

    Stack-based buffer overflow in "dnsproxy.c" in connman 1.34 and earlier allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a crafted response query string passed to the "name"...

    CVSS9.8Published29 Aug 2017
  2. 3.2%

    In ConnMan through 1.41, remote attackers able to send HTTP requests to the gweb component are able to exploit a heap-based buffer overflow in received_data to execute code.

    CVSS9.8Published3 Aug 2022
  3. 2.6%

    An issue was discovered in the DNS proxy in Connman through 1.40.

    CVSS9.1Published28 Jan 2022
  4. 2.5%

    An issue was discovered in the DNS proxy in Connman through 1.40.

    CVSS7.5Published28 Jan 2022
  5. 2.4%

    An issue was discovered in the DNS proxy in Connman through 1.40.

    CVSS9.1Published28 Jan 2022
  6. 2.0%

    In ConnMan through 1.41, a man-in-the-middle attack against a WISPR HTTP query could be used to trigger a use-after-free in WISPR handling, leading to crashes or code execution.

    CVSS8.1Published3 Aug 2022
  7. 1.3%

    A stack-based buffer overflow in dnsproxy in ConnMan before 1.39 could be used by network adjacent attackers to execute code.

    CVSS8.8Published9 Feb 2021
  8. 1.2%

    gdhcp in ConnMan before 1.39 could be used by network-adjacent attackers to leak sensitive stack information, allowing further exploitation of bugs in gdhcp.

    CVSS6.5Published9 Feb 2021
  9. 1.1%

    ConnMan 1.3 on Tizen continues to list the bluetooth service after offline mode has been enabled, which might allow remote attackers to obtain sensitive information via Bluetooth packets.

    CVSS4.3Published1 Jan 2013
  10. 1.0%

    client.c in gdhcp in ConnMan through 1.41 could be used by network-adjacent attackers (operating a crafted DHCP server) to cause a stack-based buffer overflow and denial of service, terminating the connman process.

    CVSS6.5Published12 Apr 2023
Precursor Intelligence

Running Connman? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 10 published vulnerabilities listed under the name Connman, across 127 versions.

None of Connman's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Connman. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.