VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ipmctl: vulnerability history, versions and safety

ipmctl is a package in the Debian ecosystem. Vulert records 4 vulnerabilities for it across 12 releases, from Feb 2024 to Nov 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded U4
i
4 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 ipmctl vulnerabilities

Vulert verdict on ipmctl i

Updated on 23 Oct 2026

Careful: 4 of the 4 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

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

What to do: Plan around the 4 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 4 over 1 year · 0 in the last year i
  • Latest disclosure 13 Nov 2024 i
  • Highest CVSS 7.8 i
  • With no published fix 4 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 ipmctl, 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 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 4

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

03 Vulnerabilities

Recorded vulnerabilities for ipmctl

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Escalation of Privilege Vulnerability in Intel Optane PMem Software - ipmctl Package 7.8 high No fix published 14 Feb 2024
Denial of Service Risk in Intel Optane PMem Management Software - CVE-2024-36275 N/A unrated No fix published 13 Nov 2024
Privilege Escalation Vulnerability in Intel Optane PMem Software - ipmctl Package N/A unrated No fix published 14 Feb 2024
Denial of Service Vulnerability in ipmctl Package - CVE-2024-36275 N/A unrated No fix published 13 Nov 2024

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 ipmctl

Is ipmctl safe to use?

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

How many vulnerabilities does ipmctl have?

4 vulnerabilities are recorded for ipmctl in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 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 ipmctl vulnerabilities disclosed?

0 vulnerabilities were recorded for ipmctl in the last 12 months, and the oldest entry in this database dates to 14 Feb 2024. 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 ipmctl 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 ipmctl for upcoming vulnerabilities?

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