Cyber Resilience

CVE-2025-15480

Canonical Ubuntu Desktop Provision 24.04.4

Published
09 April 2026
Modified
17 April 2026
Patch / advisory
View advisory
CVSS Score v4 2.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0031 23th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-15480 is a low-severity Exposure of Sensitive System Information Due to Uncleared Debug Information (CWE-1258) vulnerability in Canonical Ubuntu Desktop Provision. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-7 (Least Functionality) and SA-3 (System Development Life Cycle) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-15480 is a vulnerability in Ubuntu's ubuntu-desktop-provision version 24.04.4 that leads to the leakage of sensitive user credentials during crash reporting. Upon installation failure, if a user submits a bug report to Launchpad, the tool could include the user's password hash in the attached logs. This issue is categorized under CWE-1258 and carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H), indicating critical severity due to high confidentiality and availability impacts.

The vulnerability can be exploited by any unauthenticated attacker with network access to Launchpad, requiring low attack complexity and no privileges or direct user interaction from the attacker's perspective. Exploitation relies on a victim encountering an installation failure and choosing to submit a bug report, after which the password hash becomes accessible in the logs. Successful exploitation allows attackers to obtain the victim's password hash, enabling potential further credential compromise.

Mitigation is addressed in the canonical/ubuntu-desktop-provision GitHub repository through pull requests #1399 and #1400, which resolve the credential leakage in crash logs. Security practitioners should ensure affected systems are updated to patched versions of ubuntu-desktop-provision.

EU & UK References

Vulnerability Data

In Ubuntu, ubuntu-desktop-provision version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, ubuntu-desktop-provision could include the user's password hash in the attached logs.

CWE(s)
CWE-1258

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-14551Same vendor: Canonical
CVE-2024-36912Shared CWE-1258
CVE-2026-52696Shared CWE-1258
CVE-2025-32257Shared CWE-1258
CVE-2025-26482Shared CWE-1258
CVE-2024-36913Shared CWE-1258
CVE-2026-26948Shared CWE-1258
CVE-2024-6714Same product: Canonical Ubuntu Desktop Provision
CVE-2023-5182Same vendor: Canonical
CVE-2024-29069Same vendor: Canonical

Affected Assets

canonical
ubuntu desktop provision
24.04.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V13.3.3
  • V17.2.1
  • V11.2.1

Mitigating Controls (NIST 800-53 r5) AI

CM-7 Least Functionality partial match

Disabling debug and other non-essential functionality prevents the system from entering a debug state that would expose uncleared sensitive values.

SA-3 System Development Life Cycle partial match

Mandating a security-aware SDLC ensures hardware designs incorporate debug-mode clearing requirements.

SA-4 Acquisition Process partial match

Acquisition requirements can explicitly mandate secure debug behavior and data clearing in supplied hardware.

SA-8 Security and Privacy Engineering Principles partial match

Requiring security engineering principles during design directly addresses the need to clear sensitive data on debug entry.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-09 partial match
prevents

Pre-acquisition hardware integrity assessment can identify devices with uncleared debug exposure before purchase.

PR.PS-03 partial match
prevents

Hardware replacement policy can retire devices whose debug interfaces fail to clear sensitive state.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect uncleared debug information before release.

A.8.24 Use of cryptography partial match
degrades

Cryptographic key management and secure handling requirements reduce exposure of sensitive values during debug entry.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles directly address clearing of sensitive data on debug transitions.

A.8.28 Secure coding partial match
degrades

Secure coding practices can mandate explicit clearing of debug registers and memory.

A.8.33 Test information partial match
degrades

Test information protection includes ensuring debug artifacts do not leak sensitive data.

References