VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

connman: vulnerability history, versions and safety

connman is a package in the Debian ecosystem. Vulert records 32 vulnerabilities for it across 18 releases, from May 2012 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
32 vulnerabilities recorded U32
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all connman vulnerabilities

Vulert verdict on connman i

Updated on 23 Oct 2026

Careful: 2 of the 32 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 32 vulnerabilities on record across 12 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 32 over 12 years · 0 in the last year i
  • Latest disclosure 10 Apr 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for connman, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 18 of 18 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 6
  • 2013 2
  • 2017 2
  • 2021 6
  • 2022 11
  • 2023 3
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 32 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for connman

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Stack-Based Buffer Overflow in ConnMan (CVE-2021-33833) 9.8 critical 1.36-2.2 09 Jun 2021
Heap-Based Buffer Overflow in ConnMan Package - CVE-2022-32292 9.8 critical 1.36-2.2+deb11u1 03 Aug 2022
Critical Stack-Based Buffer Overflow in Connman Package 9.8 critical 1.35-1 29 Aug 2017
Out-of-Bounds Read Vulnerability in Connman DNS Proxy 9.1 critical 1.36-2.2+deb11u1 28 Jan 2022
Out-of-Bounds Read Vulnerability in Connman DNS Proxy 9.1 critical 1.36-2.2+deb11u1 28 Jan 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About connman

Is connman safe to use?

Vulert records 32 vulnerabilities for connman in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 32 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does connman have?

32 vulnerabilities are recorded for connman in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 32 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new connman vulnerabilities disclosed?

0 vulnerabilities were recorded for connman in the last 12 months, and the oldest entry in this database dates to 18 May 2012. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of connman are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor connman for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the connman version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.