# CVE-2014-1449: Other in n/a

> Remote attackers can spoof the address bar in Maxthon Cloud Browser for Android via crafted JavaScript, potentially misleading users about the site's identity.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 25 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-46c4-58c8-258m

## What is CVE-2014-1449?

CVE-2014-1449 is a medium-severity vulnerability in n/a, published on 25 Dec 2014. 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 Maxthon Cloud Browser application before 4.1.6.2000 for Android allows remote attackers to spoof the address bar via crafted JavaScript code that uses the history API.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2014-1449?

It affects 1 product.


Products: Maxthon Maxthon Cloud Browser.

## How do I fix CVE-2014-1449?

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

## Is CVE-2014-1449 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1449 and fix it if it is affected.

What it is: CVE-2014-1449 is a medium-severity vulnerability in n/a, published on 25 Dec 2014. 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-2014-1449 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-2014-1449/ (Markdown: https://insights.sbomify.com/CVE-2014-1449/index.md)
```

## Sources

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

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