dbcve.org
Yahoo\! BrowserApplication · Yahoo

CVE-2013-2307

MEDIUM · 5.8 CVSS v2.0 Published 2013-04-26
Fix available
A fix is available. Upgrade to after 1.4.2 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 Yahoo! Browser application before 1.4.3 for Android 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

This is an address bar spoofing vulnerability in the Yahoo! Browser application for Android. Attackers can craft malicious websites that display a fake URL in the address bar, tricking users into believing they are on a legitimate site. This is a UI redress vulnerability where the displayed URL does not match the actual page content being rendered.

MitigationUsers should update Yahoo! Browser for Android to version 1.4.3 or later. Until the update is applied, users should avoid trusting the address bar alone and verify URLs through other means.

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
Yahoo\! BrowserApplication
Affected:<= 1.4.2= 1.2.0

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 Yahoo! Browser in Android settings
    Open Settings on the Android device, navigate to Apps or Applications, find and tap on Yahoo! Browser in the list of installed applications
    Affected if Yahoo! Browser is installed on the device
  2. Find the installed version number
    In the App Info screen for Yahoo! Browser, look for the Version field (may be labeled as 'Version' or 'App version') and note the number displayed
    Affected if Version information is not visible or the app is not found
  3. Compare against affected versions
    Check if the installed version matches either '<=1.4.2' or exactly '1.2.0'. For example, versions 1.4.2, 1.4.1, 1.4.0, 1.3.0, 1.2.0, 1.1.0, 1.0.0 are all within the affected range
    Affected if The installed version is 1.4.2 or lower, including specifically version 1.2.0

A user is affected if Yahoo! Browser for Android is installed at version 1.4.2 or lower, including the specific version 1.2.0.

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.4.2
Interim mitigation

Users should update Yahoo! Browser for Android to version 1.4.3 or later. Until the update is applied, users should avoid trusting the address bar alone and verify URLs through other means.

Fix this in Yahoo\! Browser Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2307 — 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-2307 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