CVE-2013-1563
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 · uneditedUnspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and JavaFX 2.2.7 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Install.
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 · moderate confidenceThis is an unspecified vulnerability in the Java Runtime Environment (JRE) Install component affecting Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and JavaFX 2.2.7 and earlier. The vulnerability allows remote attackers to execute arbitrary code via unknown vectors in the installation process, impacting confidentiality, integrity, and availability.
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<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 2.2.7= 2.0= 2.0.2= 2.0.3= 2.1= 2.2= 2.2.3= 2.2.4= 2.2.5= 1.6.0= 1.6.0CVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:N/C:C/I:C/A:C
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 installed Java versionRun 'java -version' in command prompt or terminal to see the installed JRE/JDK versionAffected if Version shows 1.7.0 (Java 7) with update 17 or lower, or 1.6.0 (Java 6) with update 43 or lower
-
Identify if Java JRE or JDK is installedCheck for presence of java.exe in JRE bin folder (JRE) or both java.exe and javac.exe in JDK bin folder (JDK). On Windows, check Add/Remove Programs or registry for Java installation type.Affected if Either Oracle JRE or Oracle JDK version 1.7.0 update 17 or earlier, or 1.6.0 update 43 or earlier is installed
-
Check JavaFX version if installedLook for javafx folder in installation directory or check Java Control Panel > Java > View for JavaFX runtime version. Also check Program Files for JavaFX SDK.Affected if JavaFX version 2.2.7 or earlier, or any version 2.0.x through 2.2.5 is installed (includes 2.0, 2.0.2, 2.0.3, 2.1, 2.2, 2.2.3, 2.2.4, 2.2.5)
-
Verify installation component is presentConfirm the Java Install component exists by checking for installation-related files in the Java installation directory, typically under lib folder or installation toolsAffected if The Install component is present in the Java installation (this is the vulnerable component per the CVE)
You are affected if any Oracle or Sun JRE/JDK version 1.7.0 update 17 or earlier, or 1.6.0 update 43 or earlier, or JavaFX 2.2.7 or earlier (including 2.0 through 2.2.5) is installed on your system.
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 Java SE to versions beyond those affected (Java 7 Update 18+, Java 6 Update 44+, JavaFX 2.2.8+) or migrate to supported Java versions. Remove outdated Java installations from endpoints if no longer required.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1563 — 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-2013-1563 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