CVE-2017-10294: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer)

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer). Supported versions that are affected are 5.6.37 and earlier and 5.7.19 and earlier. Easily exploitable vulnerability allows high 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 3.0 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may disrupt the affected service.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may disrupt the affected service.

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → vulnerable operation → disrupt the affected service
Attack surface: Network
Privileges required: High: elevated access is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkDenial of service

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2017-1941Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV17-156Oracle Critical Patch updates

17-10152, CVE-2017-10153, CVE-2017-10154, CVE-2017-10155, CVE-2017-10158, CVE-2017-10159, CVE-2017-10161, CVE-2017-10162, CVE-2017-10163, CVE-2017-10164, CVE-2017-10165, CVE-2017-10166, CVE-2017-10167, CVE-2017-10190, CVE-2017-10194, CVE-2017-10197, CVE-2017-10203, CVE-2017-10227, CVE-2017-10259, CVE-2017-10260, CVE-2017-10261, CVE-2017-10263, CVE-2017-10264, CVE-2017-10265, CVE-2017-10268, CVE-2017-10270, CVE-2017-10271, CVE-2017-10274, CVE-2017-10275, CVE-2017-10276, CVE-2017-10277, CVE-2017-10279, CVE-2017-10280, CVE-2017-10281, CVE-2017-10283, CVE-2017-10284, CVE-2017-10285, CVE-2017-10286, CVE-2017-10287, CVE-2017-10292, CVE-2017-10293, CVE-2017-10294, CVE-2017-10295, CVE-2017-10296, CVE-2017-10299, CVE-2017-10300, CVE-2017-10302, CVE-2017-10303, CVE-2017-10304, CVE-2017-10306, CVE-2017-10308, CVE-2017-10309, CVE-2017-10310, CVE-2017-10311, CVE-2017-10312, CVE-2017-10313, CVE-2017-10314, CVE-2017-10315, CVE-2017-10316, CVE-2017-10317, CVE-2017-10318, CVE-2017-10319, CVE-2017-10320, CVE-2017-10321, CVE-2017-10322, CVE-2017-10323, CVE-2017-10324, CVE-2017-10325, CVE-2017-10326, CVE-2017-10327, CVE-2017-10328, CVE-2017-10329, CVE-2017-10330, CVE-2017-10331, CVE-2017-10332, CVE-2017-10333, CVE-2017-10334, CVE-2017-10335, CVE-2017-10336, CVE-2017-10337, CVE-2017-10338, CVE-2017-10339, CVE-2017

Official advisory ↗

CERT-FR · French · CERTFR-2017-AVI-367Multiples vulnérabilités dans Oracle MySQL

d?id=CVE-2017-10203 Référence CVE CVE-2017-10227 https://www.cve.org/CVERecord?id=CVE-2017-10227 Référence CVE CVE-2017-10268 https://www.cve.org/CVERecord?id=CVE-2017-10268 Référence CVE CVE-2017-10276 https://www.cve.org/CVERecord?id=CVE-2017-10276 Référence CVE CVE-2017-10277 https://www.cve.org/CVERecord?id=CVE-2017-10277 Référence CVE CVE-2017-10279 https://www.cve.org/CVERecord?id=CVE-2017-10279 Référence CVE CVE-2017-10283 https://www.cve.org/CVERecord?id=CVE-2017-10283 Référence CVE CVE-2017-10284 https://www.cve.org/CVERecord?id=CVE-2017-10284 Référence CVE CVE-2017-10286 https://www.cve.org/CVERecord?id=CVE-2017-10286 Référence CVE CVE-2017-10294 https://www.cve.org/CVERecord?id=CVE-2017-10294 Référence CVE CVE-2017-10296 https://www.cve.org/CVERecord?id=CVE-2017-10296 Référence CVE CVE-2017-10311 https://www.cve.org/CVERecord?id=CVE-2017-10311 Référence CVE CVE-2017-10313 https://www.cve.org/CVERecord?id=CVE-2017-10313 Référence CVE CVE-2017-10314 https://www.cve.org/CVERecord?id=CVE-2017-10314 Référence CVE CVE-2017-10320 https://www.cve.org/CVERecord?id=CVE-2017-10320 Référence CVE CVE-2017-10365 https://www.cve.org/CVERecord?id=CVE-2017-10365 Référence CVE CVE-2017-10378 https://www.cve.org/CVERecord?id=CVE-2017-10378 Référence CVE CVE-2017-10379 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2017-008788Oracle MySQL の MySQL Server における Server: Optimizer に関する脆弱性

Oracle MySQL の MySQL Server には、Server: Optimizer に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: MySQL Server: 5.6.37 and earlier, 5.7.19 and earlier
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 19 Oct 2017 · Last source change 4 Oct 2024, 16:54 UTC · CWE not yet assigned

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2017-1941

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceUnavailable

NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

4 Oct 2024, 16:54 UTC
Vendor guidanceAuthoritative vendor guidance changed from vendor advisory to authoritative remediation link · patch.
Before
vendor advisory
After
authoritative remediation link · patch
af854a3a-2127-422b-91ae-364da2661108 ↗
4 Oct 2024, 16:54 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
5.6.37 and earlier; 5.7.19 and earlier · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
5.6.37 and earlier; 5.7.19 and earlier · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
4 Oct 2024, 16:54 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
af854a3a-2127-422b-91ae-364da2661108 ↗
4 Oct 2024, 16:54 UTC
SeveritySeverity changed from Unknown to Medium.
Before
Unknown
After
Medium
NIST NVD ↗
4 Oct 2024, 16:54 UTC
CVSS scoreCVSS score changed from not recorded to 4.9 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
Before
not recorded
After
4.9 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
NIST NVD ↗
1 Sept 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2017-1941 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2017-1941"}
ENISA EUVD ↗
4 Oct 2024, 16:54 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2017-10-19CVE published

2024-10-04Fixed release or patch reference recorded

ENISA EUVD · EUVD-2017-1941↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer)

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2017-1941

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Optimizer)

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2017-1941

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.