CVE-2019-16681
Description
The Traveloka application 3.14.0 for Android exports com.traveloka.android.activity.common.WebViewActivity, leading to the opening of arbitrary URLs, which can inject deceptive content into the UI. (When in physical possession of the device, opening local files is also possible.) NOTE: As of 2019-09-23, the vendor has not agreed that this issue has serious impact. The vendor states that the issue is not critical because it does not allow Elevation of Privilege, Sensitive Data Leakage, or any critical unauthorized activity from a malicious user. The vendor also states that a victim must first install a malicious APK to their application.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2- Traveloka/Traveloka applicationdescription
Patches
Vulnerability mechanics
Root cause
"Improper export of an Android Activity component allows any third-party application to launch the WebView with attacker-controlled URLs."
Attack vector
Any third-party app installed on the same device (no root required) can launch the exported WebViewActivity with a crafted Intent containing arbitrary URLs. The attacker sets the Intent data to either a `file://` URI to read protected files from `/data/data/com.traveloka.android/` (requires physical device access) or a `javascript:` URI to execute arbitrary JavaScript in the WebView context [ref_id=1]. On newer Android versions, the exploit can also be triggered via Android Instant Apps directly from a web browser [ref_id=1].
Affected code
The exported Activity `com.traveloka.android.activity.common.WebViewActivity` in the Traveloka Android app (version 3.14.0 and earlier) lacks any protection mechanism. This WebView retrieves the URL directly from the Intent data and loads it without validation [ref_id=1].
What the fix does
No patch is shown in the bundle. The researcher reports that Traveloka released version 3.15.3 after the disclosure timeline, but the specific remediation is not documented [ref_id=1]. The advisory guidance is that the WebViewActivity should not be exported, or should enforce permission checks and input validation on the Intent data to prevent arbitrary URL loading [ref_id=1].
Preconditions
- configThe victim must have the vulnerable Traveloka app (version 3.14.0 or earlier) installed on their Android device
- inputFor file:// URI attacks, the attacker must have physical possession of the victim's device
- inputFor javascript: or arbitrary URL attacks, a malicious third-party app must be installed on the same device (or an Android Instant App must be used)
- authNo special permissions or root access are required on the attacker's part
Reproduction
1. Install Traveloka Android app V3.14.0 or earlier and log in with any customer account. 2. To reproduce via ADB: run `adb shell am start -n com.traveloka.android/com.traveloka.android.activity.common.WebViewActivity -d "file:///data/data/com.traveloka.android/shared_prefs/com.traveloka.android.pref_user.xml"` or `adb shell am start -n com.traveloka.android/com.traveloka.android.activity.common.WebViewActivity -d "javascript:alert\(1\)"`. 3. To reproduce via a third-party app: create an Intent with class name `com.traveloka.android.activity.common.WebViewActivity`, add `Intent.FLAG_ACTIVITY_NEW_TASK`, set the data URI to the target file or javascript URL, and call `startActivity()` [ref_id=1].
Generated on May 25, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
News mentions
0No linked articles in our index yet.