CVE-2025-5346VulnerabilityPublished 17 Jul 2025

CVE-2025-5346: kr.co.bluebird.android.bbsettings · Improper Export of Android Application Components

Affects kr.co.bluebird.android.bbsettingsSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% 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:N/SI:L/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: None
Subsequent system integrity: Low
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: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact 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 kr.co.bluebird.android.bbsettings	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately update the 'kr.co.bluebird.android.bbsettings' application to version 1.3.3 or later where the vulnerability is patched. 2) Restrict physical and local access to Bluebird devices to trusted personnel only, enforcing strict access controls and monitoring. 3) Implement device usage policies that limit installation or execution of unauthorized applications that could exploit local vulnerabilities. 4) Use Mobile Device Management (MDM) solutions to monitor device integrity and detect unauthorized changes to configuration files. 5) Conduct regular audits of device configurations and logs to identify suspicious activities. 6) If patching is delayed, consider disabling or restricting the vulnerable broadcast receiver component via device configuration or custom security policies, if feasible. 7) Train staff on the importance of device security and the risks of local exploitation. These steps go beyond generic advice by focusing on access control, monitoring, and device management tailored to the operational context of Bluebird devices.

Description

Bluebird devices contain a pre-loaded barcode scanner application. This application exposes an unsecured broadcast receiver "kr.co.bluebird.android.bbsettings.BootReceiver". A local attacker can call the receiver to overwrite file containing ".json" keyword with default barcode config file. It is possible to overwrite file in any location due to lack of protection against path traversal in name of the file. This issue affects all versions before 1.3.3.

Impact

For European organizations using Bluebird barcode scanner devices, particularly in sectors like logistics, retail, manufacturing, and healthcare where such devices are integral to operations, this vulnerability poses a risk of local privilege abuse or sabotage. An attacker with local access—such as an insider, contractor, or someone with temporary physical access—could exploit this flaw to overwrite critical configuration files, potentially causing device misconfiguration, operational disruption, or enabling further malicious activities. While the vulnerability does not directly allow remote exploitation or data exfiltration, the ability to modify device configuration files could lead to denial of service or undermine the integrity of scanned data, impacting supply chain accuracy and operational reliability. Given the specialized nature of the devices, the impact is more pronounced in environments where device availability and data integrity are critical. Additionally, compromised devices could be leveraged as footholds within secure facilities, increasing overall organizational risk.

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/07CVE-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