CVE-2012-4010
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 · uneditedOpera before 11.60 allows remote attackers to spoof the address bar via unspecified homograph characters, a different vulnerability than CVE-2010-2660.
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 confidenceOpera before 11.60 is vulnerable to address bar spoofing via unspecified homograph characters - visually similar characters from different scripts (e.g., Cyrillic letters resembling Latin characters) that trick users into believing they are visiting a legitimate website when they are actually on a malicious site.
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<= 11.60= 5.0= 5.02= 5.10= 5.11= 5.12= 6.0= 6.1= 6.01= 6.02= 6.03= 6.04CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/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 installed Opera versionOpen Opera browser, click the menu button (top-left corner), select 'Help' then 'About Opera'. The version number will be displayed in the dialog box.Affected if The version listed is 11.60 or lower, or matches 5.0, 5.02, 5.10, 5.11, 5.12, 6.0, 6.1, 6.01, 6.02, 6.03, or 6.04
-
Confirm the exact version numberNote the full version string shown in the About dialog - it may include build numbers or additional version details beyond the major.minor release.Affected if Any version at or below 11.60 is within the affected range
-
Verify the browser is Opera (not a Chromium-based successor)Confirm the browser being checked is the original Opera Browser (versions 5.x-11.x) and not Opera 12 or later, Opera Edge, or other Chromium-based Opera variants.Affected if The browser is the original Opera Browser from the affected version range
You are affected if you are running any version of the original Opera Browser from 5.0 through 11.60, as these versions contain the vulnerability to homograph-based address bar spoofing.
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 Opera browser to version 11.60 or later, which contains the patch for this homograph-based address bar spoofing vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4010 — 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-2012-4010 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