CVE-2009-2717
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 · uneditedThe Abstract Window Toolkit (AWT) implementation in Sun Java SE 6 before Update 15 on Windows 2000 Professional does not provide a Security Warning Icon, which makes it easier for context-dependent attackers to trick a user into interacting unsafely with an untrusted 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 confidenceIn Sun Java SE 6 before Update 15 on Windows 2000 Professional, the Abstract Window Toolkit (AWT) implementation fails to display a Security Warning Icon for untrusted applets. This missing visual security indicator allows context-dependent attackers to more easily impersonate trusted applications and trick users into performing unsafe actions with malicious applets.
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<= 6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Windows 2000 Professional is in useCheck the operating system version by running 'winver' or checking System Properties. The vulnerability only affects Windows 2000 Professional.Affected if The system is running Windows 2000 Professional (this is a required condition for this CVE).
-
Confirm Sun Java SE 6 is installedCheck for Java installation by looking in 'C:\Program Files\Java\' or running 'java -version' from command line.Affected if Sun Java SE 6 is installed on the system.
-
Determine Java SE 6 Update versionRun 'java -version' and check the full version string (for example: '1.6.0_14'). The Update number is the number after '_'. Alternatively, check 'C:\Program Files\Java\jre6\README.txt' or the release properties file.Affected if The Java version shows 1.6.0_X where X is less than 15 (for example, 1.6.0_14 or earlier).
-
Identify AWT applet usageReview any deployed Java applets that use AWT components (java.applet.Applet, java.awt classes). Check web browser Java plugin configurations and any local HTML files with applet tags.Affected if AWT-based applets are being run or deployed in the environment.
The environment is affected only if the system runs Windows 2000 Professional with Sun Java SE 6 version earlier than Update 15, and AWT applets are being executed.
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 Sun Java SE 6 to Update 15 or later to receive the Security Warning Icon fix. Consider upgrading from Windows 2000 Professional as it is end-of-life.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2717 — 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-2717 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