CVE-2017-3511
Last modified
CVE-2017-3511 is a vulnerability of currently unknown severity. Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: JCE). Supported versions that are affected are Java SE: 7u131 and 8u121; Java SE Embedded: 8u121; JRockit: R28.3.13. EPSS estimates a 0.76% chance of exploitation in the next 30 days.
Description
Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: JCE). Supported versions that are affected are Java SE: 7u131 and 8u121; Java SE Embedded: 8u121; JRockit: R28.3.13. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Java SE, Java SE Embedded, JRockit executes to compromise Java SE, Java SE Embedded, JRockit. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, Java SE Embedded, JRockit, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded, JRockit. Note: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It can also be exploited by supplying data to APIs in the specified Component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service. CVSS 3.0 Base Score 7.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H).
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Oracle | Jdk | 1.6 | Update 141 |
| Oracle | Jdk | 1.7 | Update 131 |
| Oracle | Jdk | 1.8 | Update 121 |
| Oracle | Jre | 1.6 | Update 141 |
| Oracle | Jre | 1.7 | Update 131 |
| Oracle | Jre | 1.8 | Update 121 |
| Oracle | Jrockit | r28.3.13 | — |
References
- http://www.securityfocus.com/bid/97731Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/97731Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3511?
How severe is CVE-2017-3511?
How do I fix CVE-2017-3511?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-3505Vulnerability in the Automatic Service Request (ASR) compone…
- CVE-2017-3506Vulnerability in the Oracle WebLogic Server component of Ora…7.4
- CVE-2017-3507Vulnerability in the Oracle Service Bus component of Oracle …
- CVE-2017-3508Vulnerability in the Primavera Gateway component of Oracle P…
- CVE-2017-3509Vulnerability in the Java SE, Java SE Embedded component of …
- CVE-2017-3510Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3512Vulnerability in the Java SE component of Oracle Java SE (su…
- CVE-2017-3513Vulnerability in the Oracle VM VirtualBox component of Oracl…
- CVE-2017-3514Vulnerability in the Java SE component of Oracle Java SE (su…
- CVE-2017-3515Vulnerability in the Oracle User Management component of Ora…
- CVE-2017-3516Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3517Vulnerability in the JD Edwards EnterpriseOne Tools componen…
Are you affected by CVE-2017-3511?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
