Flash PlayerApplication · Adobe

CVE-2007-2022

MEDIUM · 6.8 CVSS v2.0 Published 2007-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Adobe Macromedia Flash Player 7 and 9, when used with Opera before 9.20 or Konqueror before 20070613, allows remote attackers to obtain sensitive information (browser keystrokes), which are leaked to the Flash Player applet.

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 vulnerability allows Flash applets to capture browser keystrokes due to improper isolation between the browser and Flash plugin in older versions of Opera (before 9.20) and Konqueror (before 20070613). The keystrokes typed in the browser are leaked to the Flash Player applet, enabling potential information disclosure.

MitigationUpgrade Opera to version 9.20 or later, and Konqueror to version 20070613 or later. Alternatively, consider disabling Flash Player in these browsers if upgrades are not feasible.

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
Flash PlayerApplication
Affected:= 7.0.25= 8.0= 9.0.18d60= 9.0.20= 9.0.28
Opera BrowserApplication
Affected:= 5.0= 5.02= 5.10= 5.11= 5.12= 6.0= 6.1= 6.01= 6.02= 6.03= 6.04= 6.05

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
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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. Check Opera browser version
    Open Opera and navigate to Help > About Opera, or check the version from the executable properties. On Linux, run: opera --version
    Affected if Version is 5.0, 5.02, 5.10, 5.11, 5.12, 6.0, 6.1, 6.01, 6.02, 6.03, 6.04, or 6.05
  2. Check Adobe Flash Player version in Opera
    Visit a page that displays the Flash Player version, such as the Adobe Flash Player Version Test page, or check the plugin in opera:plugins
    Affected if Flash Player version is 7.0.25, 8.0, 9.0.18d60, 9.0.20, or 9.0.28
  3. Check Konqueror browser version
    Open Konqueror and go to Help > About Konqueror, or run: konqueror --version
    Affected if Version is older than the 20070613 release (check date in version string)
  4. Verify Flash is enabled in the browser
    Check the browser's plugin or extension settings to confirm the Flash Player plugin is loaded and active
    Affected if Flash Player plugin is installed and enabled in Opera or Konqueror

User is affected if running Opera versions 5.0-6.05 or Konqueror pre-20070613 with any of the listed Flash Player versions (7.0.25, 8.0, 9.0.18d60, 9.0.20, 9.0.28) enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Opera to version 9.20 or later, and Konqueror to version 20070613 or later. Alternatively, consider disabling Flash Player in these browsers if upgrades are not feasible.

Fix this in Flash Player Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2022 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2022 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