Canonical apport information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.8$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Canonical apport. Impacted is an unknown function. Executing a manipulation can lead to information disclosure. This vulnerability is tracked as CVE-2025-5054. The attack is restricted to local execution. Moreover, an exploit is present.

Detailsinfo

A vulnerability has been found in Canonical apport (affected version unknown) and classified as problematic. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces. When handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport could be made to forward the core dump to the container, potentially leaking sensitive information. `consistency_checks` is now being called before `_check_global_pid_and_forward`. Additionally, given that the PID-reuse race condition cannot be reliably detected from userspace alone, crashes are only forwarded to containers if the kernel provided a pidfd, or if the crashing process was unprivileged (i.e., if dump mode == 1).

The advisory is shared for download at seclists.org. This vulnerability was named CVE-2025-5054. The exploitation appears to be easy. The attack needs to be approached locally. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

It is possible to download the exploit at seclists.org. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-16511). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 3.8

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 4.7
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/30/2025 🔍
05/30/2025 +0 days 🔍
06/09/2025 +10 days 🔍

Sourcesinfo

Advisory: seclists.org
Status: Not defined

CVE: CVE-2025-5054 (🔍)
GCVE (CVE): GCVE-0-2025-5054
GCVE (VulDB): GCVE-100-310612
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 05/30/2025 06:01
Updated: 06/09/2025 19:14
Changes: 05/30/2025 06:01 (50), 05/31/2025 07:19 (12), 06/02/2025 21:28 (1), 06/03/2025 08:46 (2), 06/09/2025 19:14 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

 Anonymous User (+0)
1 Year ago
I don't find this cpe into NVD NIST CPE Dictionary, I instead read "apport_project:apport" or "canonical:apport". May you verify?
 VulDB Community Team1 Year ago
Thank you, we have just aligned the CPE.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!