# CVE-2019-16681: Cross-site scripting in n/a

> An exported Android activity allows opening arbitrary URLs, enabling attackers to inject deceptive content into the application's user interface.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xjgj-h9x9-m8vv

## What is CVE-2019-16681?

CVE-2019-16681 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2019-16681?

It affects 1 product.


Products: Traveloka Traveloka.

## How do I fix CVE-2019-16681?

No fix has been published for CVE-2019-16681 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-16681 being exploited?

There is no known exploitation of CVE-2019-16681 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16681 and fix it if it is affected.

What it is: CVE-2019-16681 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Sep 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16681 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-16681/ (Markdown: https://insights.sbomify.com/CVE-2019-16681/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16681
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16681
- OSV: https://osv.dev/vulnerability/CVE-2019-16681

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-16681/
Summaries are generated and may contain mistakes; the official description above is the record.
