Menu

Star on GitHub · 3.2k

CVE-2004-0627

10.0 · HIGH

The check_scramble_323 function in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to bypass authentication via a zero-length scrambled string.

Published Dec 6, 2004mysqlEPSS 69.65%

Overview

CVE-2004-0627 is a high-severity vulnerability affecting mysql mysql. It was published on December 6, 2004 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The check_scramble_323 function in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to bypass authentication via a zero-length scrambled string.

Remediation

Check the references section for vendor advisories and patches from mysql. Update mysql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2004-0627?

CVE-2004-0627 is a high-severity vulnerability affecting mysql mysql. It was published on December 6, 2004 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2004-0627?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2004-0627?

Check the references section for vendor advisories and patches from mysql. Update mysql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2004-0627?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2004-0627 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2004

View all