Skip to main content

CVE-2025-9673: Improper Export of Android Application Components in Kakao 헤이카카오 Hey Kakao App

Medium
VulnerabilityCVE-2025-9673cvecve-2025-9673
Published: Fri Aug 29 2025 (08/29/2025, 20:02:08 UTC)
Source: CVE Database V5
Vendor/Project: Kakao
Product: 헤이카카오 Hey Kakao App

Description

A vulnerability was detected in Kakao 헤이카카오 Hey Kakao App up to 2.17.4 on Android. Affected by this vulnerability is an unknown functionality of the file AndroidManifest.xml of the component com.kakao.i.connect. The manipulation results in improper export of android application components. The attack requires a local approach. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 08/29/2025, 20:32:44 UTC

Technical Analysis

CVE-2025-9673 is a medium-severity vulnerability affecting the Android application '헤이카카오 Hey Kakao App' versions 2.17.0 through 2.17.4. The vulnerability stems from improper exportation of Android application components defined in the AndroidManifest.xml file, specifically related to the component com.kakao.i.connect. Improper export means that components intended to be private or restricted are made accessible to other applications or processes on the device. This can allow a local attacker—someone with physical or logical access to the device—to interact with these components in unintended ways. The attack vector requires local access, does not require user interaction, and can be executed with low privileges, making exploitation feasible if the attacker has device access. The vulnerability does not require authentication and affects confidentiality, integrity, and availability at a low level, as indicated by the CVSS 4.8 score. The vendor Kakao was notified but did not respond, and no patches or mitigations have been published yet. The exploit details are publicly available, increasing the risk of exploitation. Since the vulnerability is related to Android application component exposure, it could allow attackers to perform unauthorized actions such as data leakage, unauthorized command execution, or privilege escalation within the app context. However, the scope is limited to local attackers and the specific app installation, reducing the overall attack surface compared to remote vulnerabilities.

Potential Impact

For European organizations, the impact depends largely on the prevalence of the Hey Kakao app among employees or users. While Kakao is a South Korean company and the app is primarily targeted at Korean-speaking users, European organizations with employees or customers using this app on Android devices could face risks. The vulnerability could lead to unauthorized access to sensitive information managed by the app or manipulation of app functions, potentially compromising user data confidentiality and integrity. In corporate environments where Bring Your Own Device (BYOD) policies are in place, compromised devices could serve as entry points for lateral movement or data exfiltration if the app is used for business communications or transactions. The local attack requirement limits remote exploitation, but physical device access or malware already present on the device could leverage this vulnerability. Additionally, the lack of vendor response and absence of patches increases the window of exposure. Organizations handling personal data of European citizens must consider GDPR implications if data leakage occurs due to this vulnerability.

Mitigation Recommendations

1. Immediate mitigation involves restricting physical and logical access to devices running the affected app versions, enforcing strong device-level authentication and encryption. 2. Organizations should audit Android devices for the presence of the Hey Kakao app and assess the necessity of its use within their environment, potentially restricting or removing it if not essential. 3. Monitor for unusual local activity on devices that could indicate exploitation attempts, including unexpected inter-app communications or abnormal app behavior. 4. Employ mobile device management (MDM) solutions to enforce app version controls and restrict installation of vulnerable versions. 5. Since no official patch is available, consider sandboxing or isolating the app environment to limit the impact of component exposure. 6. Educate users about the risks of installing apps from untrusted sources and the importance of device security hygiene. 7. Stay alert for vendor updates or third-party patches and apply them promptly once available. 8. Implement endpoint detection and response (EDR) tools capable of detecting exploitation patterns related to Android component misuse.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-08-29T10:14:10.723Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68b20afbad5a09ad007ade35

Added to database: 8/29/2025, 8:18:03 PM

Last enriched: 8/29/2025, 8:32:44 PM

Last updated: 8/29/2025, 9:02:58 PM

Views: 3

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats