CordovaApplication · Apache
CVE-2014-3500
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache Cordova Android before 3.5.1 allows remote attackers to change the start page via a crafted intent URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceApache Cordova Android before version 3.5.1 contains a vulnerability in intent URL handling that allows remote attackers to manipulate the application's start page through specially crafted intent URLs. The framework did not properly validate intent URL parameters before using them to set the launch page, enabling an attacker to redirect users to arbitrary URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CordovaApplication
<= 3.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cordova Android versionCheck the version of cordova-android in your project by examining package.json, config.xml, or the cordova.js file. Look for the version field or the Cordova platform version.Affected if The installed Cordova Android version is 3.5.0 or lower (versions prior to 3.5.1)
-
Verify intent URL handling is usedSearch your project for intent:// URL schemes in JavaScript files, HTML files, or config.xml. Look for code that uses Cordova's intent handling or URL navigation features.Affected if The application processes or navigates using intent:// URLs and the Cordova version is 3.5.0 or lower
-
Check config.xml for launch URL configurationExamine the main config.xml file in the res/xml directory for any <content> tags or navigation-related settings that define the start page. Also check for any custom intent handlers or URL handlers.Affected if The start page is dynamically set through intent URL parameters without validation and the Cordova version is vulnerable
-
Review JavaScript navigation codeLook at cordova.js or any custom JavaScript that handles URL navigation. Check for uses of window.location, navigateTo, or similar functions that process incoming intent URL parameters.Affected if The application code uses unvalidated intent URL parameters to determine navigation targets and runs on Cordova Android <= 3.5.0
You are affected if your Android application uses Apache Cordova Android version 3.5.0 or earlier and processes intent URLs without proper validation of the URL parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Apache Cordova Android to version 3.5.1 or later, which includes proper validation of intent URL parameters to prevent start page manipulation.
Fix this in Cordova
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3500 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data