dbcve.org
Jigbrowser\+Application · Jb\+

CVE-2013-2306

MEDIUM · 5.8 CVSS v2.0 Published 2013-04-26
Fix available
A fix is available. Upgrade to after 1.6.3 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The jigbrowser+ application before 1.6.4 for Android does not properly open windows, which allows remote attackers to spoof the address bar via a crafted web site.

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 · high confidence

Address bar spoofing vulnerability in jigbrowser+ for Android versions before 1.6.4. The browser fails to properly control window opening operations, allowing malicious web pages to manipulate what URL is displayed in the address bar, potentially tricking users into believing they are on a different website than they actually are.

MitigationUpgrade jigbrowser+ to version 1.6.4 or later. Users should avoid navigating to untrusted websites until the application is updated.

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
Jigbrowser\+Application
Affected:<= 1.6.3= 1.0.5= 1.1.1= 1.5.0= 1.5.5= 1.6.0= 1.6.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate jigbrowser+ on the Android device
    Open Settings > Apps > look for 'jigbrowser+' or 'Jb+ Jigbrowser+' in the installed applications list
    Affected if The application is installed on the device
  2. Determine the installed version
    Tap on the jigbrowser+ app entry and view the 'Version' or 'Version name' field displayed under the app name
    Affected if The displayed version is 1.6.3 or lower, or exactly 1.0.5, 1.1.1, 1.5.0, 1.5.5, 1.6.0, or 1.6.2
  3. Cross-check with official app store
    Open Google Play Store, search for 'jigbrowser+', and compare the listed version with your installed version
    Affected if The Play Store shows version 1.6.4 or later while your device shows an older version

If the installed version of jigbrowser+ for Android is 1.6.3 or lower, or matches any of 1.0.5, 1.1.1, 1.5.0, 1.5.5, 1.6.0, or 1.6.2, the address bar spoofing vulnerability is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.6.3
Interim mitigation

Upgrade jigbrowser+ to version 1.6.4 or later. Users should avoid navigating to untrusted websites until the application is updated.

Fix this in Jigbrowser\+ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2306 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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