# CVE-2012-6637: Security feature bypass in n/a

> Remote attackers can bypass domain whitelists in Apache Cordova and Adobe PhoneGap by using domain names with acceptable substrings, allowing unauthorized network access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gmhc-gw98-7qrj

## What is CVE-2012-6637?

CVE-2012-6637 is a high-severity vulnerability in n/a, published on 3 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Cordova 3.3.0 and earlier and Adobe PhoneGap 2.9.0 and earlier do not anchor the end of domain-name regular expressions, which allows remote attackers to bypass a whitelist protection mechanism via a domain name that contains an acceptable name as an initial substring.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-6637?

It affects 2 products.


Products: Adobe Phonegap, Apache Cordova.

## How do I fix CVE-2012-6637?

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

## Is CVE-2012-6637 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1881](https://insights.sbomify.com/CVE-2014-1881/): Security feature bypass in n/a (high 7.5)
- [CVE-2014-1882](https://insights.sbomify.com/CVE-2014-1882/): Security feature bypass in n/a (high 7.5)
- [CVE-2014-1883](https://insights.sbomify.com/CVE-2014-1883/): Security feature bypass in n/a (high 7.5)
- [CVE-2014-1884](https://insights.sbomify.com/CVE-2014-1884/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6637 and fix it if it is affected.

What it is: CVE-2012-6637 is a high-severity vulnerability in n/a, published on 3 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6637 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-2012-6637/ (Markdown: https://insights.sbomify.com/CVE-2012-6637/index.md)
```

## Sources

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

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