dbcve.org
FedoraOperating system · Fedoraproject

CVE-2010-4177

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-12
Fix available
A fix is available. Upgrade to 5.0r14 or later.
See remediation →
57/100
Remediation priority · Elevated
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
mysql-gui-tools (mysql-query-browser and mysql-admin) before 5.0r14+openSUSE-2.3 exposes the password of a user connected to the MySQL server in clear text form via the list of running processes.

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 mysql-gui-tools (mysql-query-browser and mysql-admin) versions before 5.0r14+openSUSE-2.3 pass the MySQL password as a command-line argument, causing it to be exposed in clear text when viewing the list of running processes on the system. Any local user with access to process listings (e.g., via ps, top, /proc filesystem) can retrieve the MySQL password in plaintext.

MitigationUpgrade to mysql-gui-tools 5.0r14+openSUSE-2.3 or later which handles passwords securely. If upgrading is not possible, avoid using these GUI tools and use the mysql command-line client with interactive password prompts or MySQL login-path (mysql_config_editor) instead.

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
FedoraOperating system
Affected:= 12
Mysql Gui ToolsDatabase / datastore
Affected:< 5.0r14\+opensuse-2.3

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check if mysql-gui-tools are installed
    Query your package manager (rpm -qa for RHEL/Fedora, dpkg -l for Debian) for packages named mysql-gui-tools, mysql-query-browser, or mysql-admin
    Affected if Any of these packages are installed on the system
  2. Check the installed version of mysql-query-browser
    Run 'rpm -q mysql-query-browser' (Fedora/RHEL) or check package version via your package manager
    Affected if Version exists but is earlier than 5.0r14+openSUSE-2.3
  3. Check the installed version of mysql-admin
    Run 'rpm -q mysql-admin' (Fedora/RHEL) or check package version via your package manager
    Affected if Version exists but is earlier than 5.0r14+openSUSE-2.3
  4. Inspect running processes for plaintext passwords
    Run 'ps aux | grep mysql' or view /proc/<pid>/cmdline for any mysql-query-browser or mysql-admin processes
    Affected if Any running process shows a MySQL password as a command-line argument

The system is affected if mysql-query-browser or mysql-admin with version earlier than 5.0r14+openSUSE-2.3 is installed, or if running processes expose MySQL passwords in the command line.

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.0r14 or later
Fixed in 5.0r14
Interim mitigation

Upgrade to mysql-gui-tools 5.0r14+openSUSE-2.3 or later which handles passwords securely. If upgrading is not possible, avoid using these GUI tools and use the mysql command-line client with interactive password prompts or MySQL login-path (mysql_config_editor) instead.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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