CVE-2015-2575
UnknownEPSS 3.59%
Last modified
CVE-2015-2575 is a vulnerability of currently unknown severity. Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J.. EPSS estimates a 3.59% chance of exploitation in the next 30 days.
Description
Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Debian | Debian Linux | 8.0 | — |
| Suse | Linux Enterprise Desktop | 11 | Sp3 |
| Suse | Linux Enterprise Server | 11 | Sp3 |
| Suse | Linux Enterprise Software Development Kit | 11 | Sp3 |
| Mysql | Mysql | <= 5.1.34 | — |
References
- http://lists.opensuse.org/opensuse-security-announce/2015-05/msg00026.htmlThird Party Advisory
- http://www.debian.org/security/2016/dsa-3621Third Party Advisory
- http://www.securityfocus.com/bid/74075Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1032121Third Party Advisory, VDB Entry
- http://lists.opensuse.org/opensuse-security-announce/2015-05/msg00026.htmlThird Party Advisory
- http://www.debian.org/security/2016/dsa-3621Third Party Advisory
- http://www.securityfocus.com/bid/74075Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1032121Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2015-2575?
Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J.
How severe is CVE-2015-2575?
Severity scoring for CVE-2015-2575 is pending analysis. The EPSS model estimates a 3.59% probability of exploitation in the next 30 days.
How do I fix CVE-2015-2575?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
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 2015
- CVE-2015-2569Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2015-2570Unspecified vulnerability in the Oracle Demand Planning comp…
- CVE-2015-2571Unspecified vulnerability in Oracle MySQL Server 5.5.42 and …
- CVE-2015-2572Unspecified vulnerability in the Oracle Hyperion Smart View …
- CVE-2015-2573Unspecified vulnerability in Oracle MySQL Server 5.5.41 and …
- CVE-2015-2574Unspecified vulnerability in Oracle Sun Solaris 10 allows lo…
- CVE-2015-2576Unspecified vulnerability in the MySQL Utilities component i…
- CVE-2015-2577Unspecified vulnerability in Oracle Sun Solaris 10 allows lo…
- CVE-2015-2578Unspecified vulnerability in Oracle Sun Solaris 11.2 allows …
- CVE-2015-2579Unspecified vulnerability in the Oracle Health Sciences Argu…
- CVE-2015-2580Unspecified vulnerability in Oracle Sun Solaris 10 and 11.2 …
- CVE-2015-2581Unspecified vulnerability in the Oracle Secure Global Deskto…
Are you affected by CVE-2015-2575?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST