CVE-2009-2068
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 · uneditedGoogle Chrome detects http content in https web pages only when the top-level frame uses https, which allows man-in-the-middle attackers to execute arbitrary web script, in an https site's context, by modifying an http page to include an https iframe that references a script file on an http site, related to "HTTP-Intended-but-HTTPS-Loadable (HPIHSL) pages."
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 confidenceGoogle Chrome fails to properly detect mixed HTTP content (scripts, iframes) loaded in HTTPS pages when the top-level frame uses HTTPS. Attackers on the same network can modify HTTP pages to inject HTTPS iframes that load scripts from HTTP sources, allowing arbitrary script execution in the context of the trusted HTTPS 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= 5..10= 5.0= 5.1= 5.02= 5.2= 5.3= 5.4= 5.5= 5.6= 5.7= 5.8= 5.9CVSS 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.
-
Check if Opera browser is installedSearch for Opera executable in common installation paths: Windows (C:\Program Files\Opera\opera.exe, C:\Program Files (x86)\Opera\opera.exe), Linux (/usr/bin/opera, /usr/local/bin/opera), Mac (/Applications/Opera.app). On Windows, also check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Opera or use 'wmic product' command.Affected if Opera browser is found on the system
-
Determine installed Opera versionRun 'opera --version' from command line, or right-click opera.exe > Properties > Details tab, or check the uninstall entry in Windows registry under the Opera uninstall key.Affected if Version is 5.0, 5.02, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, or 10.x (any subversion of 10)
-
Verify if Opera is used for browsing HTTPS sitesReview browser usage or check if Opera is set as the default browser. Inspect any saved browser history or bookmarks that contain HTTPS URLs.Affected if User browses HTTPS websites using an affected Opera version
User is affected if Opera versions 5.0 through 5.9 or any 10.x version is installed and used to browse HTTPS pages that could load mixed HTTP content.
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 dataUpdate Google Chrome to a version that properly enforces mixed content blocking and Content Security Policy headers to prevent HTTP resources from loading in HTTPS contexts.
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 h
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 locallyCheck whether your project pulls in CVE-2009-2068 — 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-2009-2068 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