dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2014-2484

MEDIUM · 6.5 CVSS v2.0 Published 2014-07-17
Fix available
A fix is available. Upgrade to after 5.6.17 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.6.17 and earlier allows remote authenticated users to affect confidentiality, integrity, and availability via vectors related to SRFTS.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unspecified vulnerability in Oracle MySQL Server 5.6.17 and earlier related to the SRFTS (Secure Remote File Transfer System) component. Exploitable by remote authenticated users, allowing impact to confidentiality, integrity, and availability with medium complexity.

MitigationUpgrade MySQL Server to version 5.6.18 or later to obtain the security patch. Additionally, apply least-privilege principles for database user accounts and restrict network access to the MySQL service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:<= 5.6.17= 5.6.0= 5.6.1= 5.6.2= 5.6.3= 5.6.4= 5.6.5= 5.6.6= 5.6.7= 5.6.8= 5.6.9= 5.6.10
Linux Enterprise DesktopOperating system
Affected:= 11.0
Linux Enterprise ServerOperating system
Affected:= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MySQL server version
    Run command: mysql --version or SELECT VERSION();
    Affected if Version is 5.6.17 or earlier, or matches 5.6.0 through 5.6.10 exactly
  2. Identify if MySQL service is running
    Execute: ps aux | grep mysql or systemctl status mysql
    Affected if MySQL process is active on the system
  3. Locate MySQL binary and configuration files
    Check common paths: /var/lib/mysql, /etc/mysql/my.cnf, /usr/sbin/mysqld
    Affected if MySQL installation found at standard locations indicating active deployment
  4. Verify SRFTS component status
    Query: SHOW VARIABLES LIKE 'have_srfts'; or examine MySQL plugins directory for srfts-related files
    Affected if SRFTS is enabled or the srfts plugin/feature is present in the MySQL installation

System is affected if MySQL Server version 5.6.17 or earlier (including 5.6.0-5.6.10) is installed AND the SRFTS component is enabled, with network accessibility allowing remote authenticated connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.6.17
Interim mitigation

Upgrade MySQL Server to version 5.6.18 or later to obtain the security patch. Additionally, apply least-privilege principles for database user accounts and restrict network access to the MySQL service.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2484 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data