CVE-2017-3273
Last modified
CVE-2017-3273 is a vulnerability of currently unknown severity. Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DDL). Supported versions that are affected are 5.6.34 and earlier and 5.7.16 and earlier. EPSS estimates a 3.09% chance of exploitation in the next 30 days.
Description
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DDL). Supported versions that are affected are 5.6.34 and earlier and 5.7.16 and earlier. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 6.5 (Availability impacts).
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oracle | Mysql | >= 5.6.0, <= 5.6.34 |
| Oracle | Mysql | >= 5.7.0, <= 5.7.16 |
References
- http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/95583Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037640Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2787Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2886Third Party Advisory
- https://security.gentoo.org/glsa/201702-17Third Party Advisory
- http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.htmlPatch, Vendor Advisory
- http://www.securityfocus.com/bid/95583Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037640Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2787Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2886Third Party Advisory
- https://security.gentoo.org/glsa/201702-17Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3273?
How severe is CVE-2017-3273?
How do I fix CVE-2017-3273?
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-3267Vulnerability in the Oracle Outside In Technology component …
- CVE-2017-3268Vulnerability in the Oracle Outside In Technology component …
- CVE-2017-3269Vulnerability in the Oracle Outside In Technology component …
- CVE-2017-3270Vulnerability in the Oracle Outside In Technology component …
- CVE-2017-3271Vulnerability in the Oracle Outside In Technology component …
- CVE-2017-3272Vulnerability in the Java SE, Java SE Embedded component of …
- CVE-2017-3274Vulnerability in the Oracle Email Center component of Oracle…
- CVE-2017-3275Vulnerability in the Oracle Email Center component of Oracle…
- CVE-2017-3276Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-3277Vulnerability in the Oracle Applications Manager component o…
- CVE-2017-3278Vulnerability in the Oracle One-to-One Fulfillment component…
- CVE-2017-3279Vulnerability in the Oracle Leads Management component of Or…
Are you affected by CVE-2017-3273?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
