CVE-2006-6984
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 · uneditedCross-domain vulnerability in GreenBrowser 3.4.0622 allows remote attackers to access restricted information from other domains via an object tag with a data parameter that references a link on the attacker's originating site that specifies a Location HTTP header that references the target site, which then makes that content available through the outerHTML attribute of the object, a similar vulnerability to CVE-2006-3280.
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 confidenceCross-domain information disclosure vulnerability in GreenBrowser 3.4.0622 where the browser improperly enforces same-origin policy on object tags. Attackers can exploit this by embedding an object tag with a data parameter pointing to a URL on their domain that uses a Location HTTP header redirect to the target site, then reading the redirected content via the object's outerHTML attribute.
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= 3.4.0622CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Confirm GreenBrowser installationCheck for GreenBrowser executable (greenbrowser.exe) in common installation directories such as C:\Program Files\GreenBrowser or C:\Program Files (x86)\GreenBrowser, or search the system for the executableAffected if GreenBrowser is found installed on the system
-
Identify GreenBrowser versionLocate greenbrowser.exe, right-click and select Properties, then check the Version tab, or run the executable and look for version information in the browser's About dialog (typically via Help menu)Affected if The installed version is exactly 3.4.0622
-
Verify vulnerability trigger conditionThis is a browser behavior vulnerability where the same-origin policy is not enforced on object tags. The flaw is present in version 3.4.0622 regardless of configuration; it manifests when the browser processes an object tag with a data attribute pointing to a URL that performs an HTTP redirectAffected if GreenBrowser version 3.4.0622 is in use and the browser processes external web content with object tags
A user is affected if GreenBrowser version 3.4.0622 is installed and actively used to browse web content, as the same-origin policy weakness is inherent to that specific version.
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 dataThis is a browser-level vulnerability in an older browser (circa 2006). Primary mitigation is to migrate away from GreenBrowser to a modern, actively maintained browser with proper same-origin policy enforcement.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6984 — 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-2006-6984 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