dbcve.org
Zrm For My SqlApplication · Zmanda

CVE-2009-3102

HIGH · 10.0 CVSS v2.0 Published 2009-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The doHotCopy subroutine in socket-server.pl in Zmanda Recovery Manager (ZRM) for MySQL 2.x before 2.1.1 allows remote attackers to execute arbitrary commands via vectors involving a crafted $MYSQL_BINPATH variable.

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 · high confidence

The doHotCopy subroutine in socket-server.pl of Zmanda Recovery Manager (ZRM) for MySQL 2.x fails to properly sanitize the $MYSQL_BINPATH variable before using it in a system call, allowing remote attackers to inject and execute arbitrary commands on the host system.

MitigationUpgrade to ZRM for MySQL version 2.1.1 or later which contains the patched code. If immediate patching is not possible, restrict network access to the ZRM server and disable the socket-server.pl interface.

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
Zrm For My SqlApplication
Affected:= 2.1

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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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. Verify ZRM for MySQL installation
    Look for Zmanda Recovery Manager for MySQL installation directories such as /usr/bin/zrm, /opt/zmanda/zrm, or C:\Program Files\Zmanda\ZRM. Check for presence of ZRM binaries and configuration files.
    Affected if ZRM for MySQL is installed on the system.
  2. Determine installed version
    Run the ZRM version command if available (e.g., zrm --version, zmanda --version, or check /usr/bin/zrm --version). Alternatively, inspect the main ZRM executable or read any version file in the installation directory.
    Affected if The installed version is exactly 2.1.
  3. Locate socket-server.pl
    Search for the file socket-server.pl in the ZRM installation directory, typically found under /usr/lib/mysql-zrm/plugins/ or /opt/zmanda/zrm/plugins/. Verify its presence.
    Affected if socket-server.pl exists in the ZRM plugins directory.
  4. Check if socket-server service is active
    Inspect running processes for mysql-zrm-socket or socket-server.pl. Also check /etc/init.d/ for startup scripts related to ZRM socket service. Look for any listener on port 25300 or similar ports used by ZRM.
    Affected if The socket-server.pl process is running or the socket listener is enabled.

The system is affected if ZRM for MySQL version 2.1 is installed with socket-server.pl present and the socket service active or accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ZRM for MySQL version 2.1.1 or later which contains the patched code. If immediate patching is not possible, restrict network access to the ZRM server and disable the socket-server.pl interface.

Recommended fix High confidence

ZRM for MySQL 2.1.1 or later

  1. 1. Identify the currently installed ZRM for MySQL version using 'rpm -qa | grep zrm' or checking the application version
  2. 2. Download ZRM for MySQL version 2.1.1 or later from the official Zmanda repository or download page
  3. 3. Back up the existing ZRM configuration and database
  4. 4. Install the updated package using the appropriate package manager (e.g., 'rpm -Uvh zrm-2.1.1-1.noarch.rpm' for RPM-based systems)
  5. 5. Verify the installation by checking the new version number
  6. 6. Test the socket-server.pl functionality to ensure the application works correctly with the updated version
  7. 7. Review the $MYSQL_BINPATH configuration to ensure proper input validation is in place
Caveat Review release notes for any configuration changes between versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zrm For My Sql Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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