LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3259: Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Deployment).

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Deployment). Supported versions that are affected are Java SE: 6u131, 7u121 and 8u112. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS v3.0 Base Score 3.7 (Confidentiality impacts).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-3259 is an Oracle Java SE Deployment flaw affecting specific old Java releases. It matters mainly on clients that run untrusted sandboxed Java Web Start applications or applets. A successful attack could expose some Java-accessible data, not full system control based on the provided sources. Exposure is most likely on legacy endpoint or workstation environments that still support Java Web Start or sandboxed Java applets from untrusted sources. Server-side Java applications that only run trusted deployed code are explicitly described as out of scope by Oracle. Treat this as a legacy client-risk cleanup item, not an emergency based on available evidence. Prioritize environments that still allow untrusted Java applets or Web Start, especially on user workstations handling sensitive information. Mitigation focus: Inventory Java SE 6u131, 7u121, and 8u112 across endpoints.; Apply Oracle CPU January 2017 or relevant vendor-packaged Java updates.; Disable or remove Java applet and Web Start support where unnecessary..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-3259 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OracleJava SE6u131, 7u121, 8u112Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.