Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2004-0957: Unknown vulnerability in MySQL 3.23.58 and earlier, when a local user has privileges for a database whose name

50
This month
MEDIUM 6.8WATCHLISTDOWNGRADEDOWNGRADEMITIGATE

CVE-2004-0957 is a medium-severity flaw (CVSS 6.8) affecting openpkg, mysql, enterprise linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Unknown vulnerability in MySQL 3.23.58 and earlier, when a local user has privileges for a database whose name includes a "_" (underscore), grants privileges to other databases that have similar names, which can allow the user to conduct unauthorized activities.

Why this priority

  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score6.8 (Medium)
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
Published2005-02-09
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: openpkg · oracle · redhat · suse · trustix

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

openpkg openpkg DOWNGRADE
Affected: 2.1 · 2.2 · current
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1
1. Check installed version
apt-cache policy openpkg || rpm -q openpkg || openpkg --version
2. No fixed release: DOWNGRADE to a release before 2.1 (Debian / Ubuntu)
apt-cache madison openpkg sudo apt install openpkg=<VERSION_BEFORE_2.1> sudo apt-mark hold openpkg
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openpkg sudo dnf downgrade openpkg-<VERSION_BEFORE_2.1> sudo dnf versionlock add openpkg
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle mysql DOWNGRADE
Affected: 3.20 · 3.20.32a · 3.21 · 3.22 · 3.22.26 · 3.22.27 · 3.22.28 · 3.22.29
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.20
1. Check installed version
apt-cache policy mysql || rpm -q mysql || mysql --version
2. No fixed release: DOWNGRADE to a release before 3.20 (Debian / Ubuntu)
apt-cache madison mysql sudo apt install mysql=<VERSION_BEFORE_3.20> sudo apt-mark hold mysql
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mysql sudo dnf downgrade mysql-<VERSION_BEFORE_3.20> sudo dnf versionlock add mysql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat enterprise linux MITIGATE
Affected: 3.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux desktop MITIGATE
Affected: 3.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
suse suse linux MITIGATE
Affected: 8.0 · 8.1 · 8.2 · 9.0 · 9.1 · 9.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
trustix secure linux MITIGATE
Affected: 1.5 · 2.0 · 2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.5
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2004-0957?

openpkg: downgrade or apply the listed mitigation; mysql: downgrade or apply the listed mitigation; enterprise linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-0957 being exploited?

CVE-2004-0957 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2004-0957 affect?

CVE-2004-0957 affects openpkg, mysql, enterprise linux. Severity is medium (CVSS 6.8). Unknown vulnerability in MySQL 3.23.58 and earlier, when a local user has privileges for a database whose name includes a "_" (underscore), grants privileges to other databases that have similar names, which can allow the user to conduct un

How urgent is CVE-2004-0957?

Priority 50/100. On your watchlist

Software pages

MySQL vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.