CVE-2017-3509
Last modified
CVE-2017-3509 is a vulnerability of currently unknown severity. Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Networking). Supported versions that are affected are Java SE: 6u141, 7u131 and 8u121; Java SE Embedded: 8u121. EPSS estimates a 2.21% chance of exploitation in the next 30 days.
Description
Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Networking). Supported versions that are affected are Java SE: 6u141, 7u131 and 8u121; Java SE Embedded: 8u121. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE, Java SE Embedded accessible data as well as unauthorized read access to a subset of Java SE, Java SE Embedded 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 3.0 Base Score 4.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).
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 |
References
- http://www.securityfocus.com/bid/97737Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/97737Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3509?
How severe is CVE-2017-3509?
How do I fix CVE-2017-3509?
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-3503Vulnerability in the Primavera P6 Enterprise Project Portfol…
- CVE-2017-3504Vulnerability in the Automatic Service Request (ASR) compone…
- 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-3510Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3511Vulnerability in the Java SE, Java SE Embedded, JRockit comp…
- 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…
Are you affected by CVE-2017-3509?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
