CVE-2005-0083: n/a vulnerability

CVE-2005-0083: MySQL MaxDB 7.5.00 for Windows, and possibly earlier versions and other platforms, allows remote attackers...

MySQL MaxDB 7.5.00 for Windows, and possibly earlier versions and other platforms, allows remote attackers to cause a denial of service (application crash) via invalid parameters to the (1) DBMCli_String::ReallocString, (2) DBMCli_String::operator, (3) DBMCli_Buffer::ForceResize, (4) DBMCli_Wizard::InstallDatabase, (5) DBMCli_Devspaces::Complete, (6) DBMWeb_TemplateWizard::askForWriteCountStep5, or (7) DBMWeb_DBMWeb::wizardDB functions, which triggers a null dereference.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 20:57 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2005-0083 describes a remote denial-of-service issue in MySQL MaxDB 7.5.00 on Windows, with possible impact to earlier versions or other platforms. Malformed inputs can crash the application. The main business risk is availability loss for systems still running exposed MaxDB management components. Exposure is most likely in legacy environments running MySQL MaxDB 7.5.00, especially Windows deployments with DBM/Web Agent management interfaces reachable by untrusted networks. The record is from 2005, so modern exposure should be uncommon but may persist in neglected systems. Prioritize if legacy MaxDB supports business-critical services or is reachable outside trusted networks. The issue is availability-focused, not confirmed as data theft or code execution, but unsupported database management software should be removed from exposed paths quickly. Mitigation focus: Inventory systems for MySQL MaxDB 7.5.00 and related legacy deployments.; Restrict DBM/Web Agent access to trusted administrative networks only.; Check vendor or maintainer guidance for supported upgrade or patch paths..

Prepared: Jun 29, 2026, 23:27 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-0083 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Mar 17, 2005, 05:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
maxdb-null-pointer-dos(19687)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.