CVE-2025-5345VulnerabilityPublished 17 Jul 2025

CVE-2025-5345: com.bluebird.filemanagers · Improper Export of Android Application Components

Affects com.bluebird.filemanagersSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: High
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Bluebird com.bluebird.filemanagers	Affected =1.4.4	Fixed in–

AI-suggested

1. Immediate mitigation involves restricting physical and local access to Bluebird devices to trusted personnel only, minimizing the risk of local exploitation. 2. Disable or restrict access to the vulnerable service "com.bluebird.system.koreanpost.IsdcardRemoteService" if possible, either through device management policies or by uninstalling or disabling the file manager application if it is not essential. 3. Monitor device logs and behavior for unusual file operations or service bindings that could indicate exploitation attempts. 4. Employ Mobile Device Management (MDM) solutions to enforce strict application control policies and limit installation or execution of unauthorized applications. 5. Regularly audit devices for installed versions of the Bluebird file manager and avoid upgrading to version 1.4.4 until a secure patch is released; consider downgrading to version 1.3.6 as recommended by the vendor. 6. Educate staff about the risks of local device access and enforce strong physical security controls in environments where these devices are deployed. 7. Stay updated with vendor advisories and apply patches promptly once available. 8. For critical deployments, consider network segmentation and data encryption to limit the impact of potential device compromise.

Description

Bluebird devices contain a pre-loaded file manager application. This application exposes an unsecured service provider "com.bluebird.system.koreanpost.IsdcardRemoteService". A local attacker can bind to the AIDL-type service to copy and delete arbitrary files from device's storage with system-level permissions. Version 1.4.4 is vulnerable, vendor reverted vulnerable versions to older version: 1.3.6

Impact

For European organizations, the impact of this vulnerability depends largely on the deployment of Bluebird devices within their operational environments. Bluebird devices are often used in specialized industrial, logistics, or retail sectors for their ruggedness and specialized features. If these devices are used to handle sensitive data or critical operations, the vulnerability could lead to unauthorized data access, deletion of important files, or disruption of business processes. The ability to manipulate files with system-level permissions could also facilitate further attacks, such as implanting malware or disrupting device functionality. Given the local attack vector, the threat is more pronounced in environments where devices are physically accessible by untrusted personnel or in scenarios where insider threats exist. The lack of a patch means organizations must rely on mitigations until a secure update is released. The high scope impact means that a successful exploit could affect multiple components or data stores on the device, raising concerns about data confidentiality, integrity, and availability. European organizations in sectors like manufacturing, logistics, or field services using Bluebird devices should be particularly vigilant.

CWE-926Improper Export of Android Application Components (opens in a new tab)
Variant weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.
Build and Compilation · Attack Surface Reduction
If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest.
Build and Compilation · Attack Surface Reduction
If you only intend to use exported components between related apps under your control, use android:protectionLevel="signature" in the xml manifest to restrict access to applications signed by you.
Build and Compilation · Architecture and Design · Attack Surface Reduction
Limit Content Provider permissions (read/write) as appropriate.
OWASP Cheat Sheets
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert.pl/en/posts/2025/07/CVE-2025-5344 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jul 2025, 13:31 UTC

WeaknessesCWE-926

Technical details

References

Community reviews

Related threats