CVE-2017-3635
Last modified
CVE-2017-3635 is a vulnerability of currently unknown severity. Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/C). Supported versions that are affected are 6.1.10 and earlier. EPSS estimates a 2.03% chance of exploitation in the next 30 days.
Description
Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/C). Supported versions that are affected are 6.1.10 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Connectors. Note: The documentation has also been updated for the correct way to use mysql_stmt_close(). Please see: https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-execute.html, https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-fetch.html, https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-close.html, https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-error.html, https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-errno.html, and https://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-sqlstate.html. CVSS 3.0 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oracle | Mysql | >= 5.5.0, <= 5.5.56 |
| Oracle | Mysql | >= 5.6.0, <= 5.6.36 |
| Oracle | Mysql | >= 5.7.0, <= 5.7.18 |
| Oracle | Mysql Connector\/C | <= 6.1.10 |
| Debian | Debian Linux | 8.0 |
References
- http://www.debian.org/security/2017/dsa-3922Third Party Advisory
- http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/99730Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038928Third Party Advisory, VDB Entry
- http://www.debian.org/security/2017/dsa-3922Third Party Advisory
- http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/99730Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038928Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3635?
How severe is CVE-2017-3635?
How do I fix CVE-2017-3635?
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-3629Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3630Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3631Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3632Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3633Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3634Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3636Vulnerability in the MySQL Server component of Oracle MySQL …5.3
- CVE-2017-3637Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3638Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3639Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3640Vulnerability in the MySQL Server component of Oracle MySQL …
- CVE-2017-3641Vulnerability in the MySQL Server component of Oracle MySQL …4.9
Are you affected by CVE-2017-3635?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
