CVE-2014-5318
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 · uneditedThe jigbrowser+ application 1.8.1 and earlier for iOS allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code.
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 confidenceThe jigbrowser+ application for iOS versions 1.8.1 and earlier contains a Same Origin Policy (SOP) bypass vulnerability. Attackers can exploit this by tricking users into running crafted JavaScript code, allowing the malicious script to access resources from other origins that should normally be protected by SOP隔离.
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<= 1.8.1= 1.8.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/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 the installed jigbrowser+ versionOpen the iOS Settings app, navigate to General > iPhone Storage (or iPad Storage), find jigbrowser+ in the list, and view the version number displayed. Alternatively, open the App Store app, search for jigbrowser+, and check the version listed under the app name.Affected if The displayed version is 1.8.1, 1.8.0, or any version number lower than 1.8.1 (for example, 1.7.x, 1.6.x, etc.)
-
Confirm the app is the jigbrowser+ browserVerify that the application name matches exactly 'jigbrowser+' or 'Jigbrowser+' (with the plus sign). This vulnerability affects only the jigbrowser+ application, not other browsers.Affected if The app is jigbrowser+ with version 1.8.1 or earlier.
-
Verify the SOP bypass condition existsThis vulnerability is a Same Origin Policy bypass that enables crafted JavaScript to access resources from other origins. The condition for exploitation requires the browser to be running untrusted JavaScript content.Affected if The browser is used to navigate to untrusted websites containing JavaScript while running version 1.8.1 or earlier.
A user is affected if jigbrowser+ version 1.8.1 or earlier is installed on iOS, regardless of whether untrusted content has been accessed yet.
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 dataUsers should upgrade jigbrowser+ to a version newer than 1.8.1. If upgrade is not immediately possible, avoid untrusted websites and JavaScript-heavy content within the browser application.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5318 — 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-5318 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