dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2013-0375

MEDIUM · 5.4 CVSS v3.1 Published 2013-01-17
Fix available
A fix is available. Upgrade to 5.1.67 / 5.2.14 or later.
See remediation →
60/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 Server component in Oracle MySQL 5.1.66 and earlier, and 5.1.28 and earlier, allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Server Replication.

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 MySQL Server Replication allows remote authenticated users to affect confidentiality and integrity via unknown vectors. The flaw affects MySQL versions 5.1.66 and earlier (and 5.1.28 and earlier), targeting the replication functionality.

MitigationUpgrade MySQL to a version beyond 5.1.66 (preferably to a supported branch like 5.5, 5.6, 5.7, or 8.x) and apply relevant Oracle Critical Patch Updates. Additionally, restrict replication user privileges and network access to replication-related ports.

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.1.0, <= 5.1.66
MariaDBDatabase / datastore
Affected:>= 5.1.0, < 5.1.67>= 5.2.0, < 5.2.14>= 5.3.0, < 5.3.12
Ubuntu LinuxOperating system
Affected:= 10.04= 11.10= 12.04= 12.10
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux EusOperating system
Affected:= 6.3
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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. Identify MySQL or MariaDB installation and version
    Run `mysql --version` or `mysqld --version` from the command line, or check the installed package version using the system package manager (e.g., `dpkg -l | grep mysql`, `rpm -qa | grep mysql`, or equivalent for your distribution)
    Affected if The installed version falls within 5.1.0 to 5.1.66 for MySQL, or within the affected MariaDB ranges (5.1.0 to <5.1.67, 5.2.0 to <5.2.14, or 5.3.0 to <5.3.12)
  2. Confirm replication functionality is in use
    Connect to MySQL as an administrative user and run `SHOW PROCESSLIST` to view active threads, or check replication status with `SHOW SLAVE STATUS` (or `SHOW REPLICA STATUS` for newer versions) and `SHOW MASTER STATUS`
    Affected if Replication threads (Slave_IO_Running, Slave_SQL_Running) are present and active, indicating replication is configured and running
  3. Verify replication master configuration
    Check the MySQL configuration file (typically /etc/mysql/my.cnf or /etc/my.cnf) for replication-related settings such as `server-id`, `log-bin`, `binlog-do-db`, or `replicate-do-db` under the `[mysqld]` section
    Affected if Replication master settings are present in the configuration file, meaning the server is configured as a replication master
  4. Check replication slave configuration
    Examine the MySQL configuration file for `relay-log`, `relay-log-replay`, `replicate-*` options, or check the `mysql.slave_master_info` and `mysql.slave_relay_log_info` system tables if they exist
    Affected if Replication slave settings are configured, meaning the server receives replicated data from a master

You are affected if your MySQL version is between 5.1.0 and 5.1.66 (or your MariaDB version falls within the specified vulnerable ranges) AND replication is actively configured or running on your server.

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 5.1.67 / 5.2.14 / 5.3.12 or later
Fixed in 5.1.675.2.145.3.12
Interim mitigation

Upgrade MySQL to a version beyond 5.1.66 (preferably to a supported branch like 5.5, 5.6, 5.7, or 8.x) and apply relevant Oracle Critical Patch Updates. Additionally, restrict replication user privileges and network access to replication-related ports.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,590
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0375 — 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-2013-0375 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