CVE-2006-0369: n/a vulnerability

CVE-2006-0369: MySQL 5.0.18 allows local users with access to a VIEW to obtain sensitive information via the "SELECT * FRO...

MySQL 5.0.18 allows local users with access to a VIEW to obtain sensitive information via the "SELECT * FROM information_schema.views;" query, which returns the query that created the VIEW. NOTE: this issue has been disputed by third parties, saying that the availability of the schema is a normal and sometimes desired aspect of database access

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 16:34 UTC (UTC+00:00)

Security readout for executives and security teams

This historical MySQL issue concerns exposure of view definitions to local database users who can access a view. The disclosed data is metadata, but it could matter if view definitions reveal sensitive table names, logic, or embedded values. The issue is disputed as potentially normal database behavior. Likely exposure is limited to environments still running MySQL 5.0.18 with local authenticated database users who can access VIEW objects. The source bundle does not identify broader affected versions, CPEs, cloud services, or default-exposed remote attack paths. Treat this as a low-priority legacy exposure check unless MySQL 5.0.18 is still in use or view definitions contain sensitive information. The main business risk is disclosure of database design or embedded sensitive logic to already-authorized users. Mitigation focus: Inventory systems for MySQL 5.0.18 or legacy MySQL deployments.; Review vendor guidance before assuming a patch or configuration fix.; Limit VIEW access to users with a business need..

Prepared: Jun 29, 2026, 15:05 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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2006-0369 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: Jan 22, 2006, 20: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

1Source 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

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.