LiveActive security incident?Get immediate response
CVE Record

CVE-2009-20004: gAlan <= 0.2.1 Buffer Overflow

gAlan 0.2.1, a modular audio processing environment for Windows, is vulnerable to a stack-based buffer overflow when parsing .galan files. The application fails to properly validate the length of input data, allowing a specially crafted file to overwrite the stack and execute arbitrary code. Exploitation requires local interaction, typically by convincing a user to open the malicious file.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2009-20004 is a legacy Windows application flaw in gAlan 0.2.1 involving malicious .galan project files. A user must open a crafted file, but successful exploitation could run attacker-controlled code on that workstation. Exposure is likely narrow unless the software remains installed in audio or legacy environments.

Executive priority

Prioritize as a high-severity legacy exposure. The business urgency is highest for environments with old Windows workstations, creative/audio workflows, or weak attachment controls. If gAlan is absent, residual risk is low.

Technical view

The issue is reported as a stack-based buffer overflow in gAlan's .galan file parsing, mapped to CWE-121. The CVSS 4.0 score is 8.4 with local attack vector and active user interaction. Public exploit references exist, but the bundle does not show CISA KEV listing or active exploitation evidence.

Likely exposure

Most organizations are exposed only if Windows endpoints still have gAlan 0.2.1 or earlier, or users can open received .galan files. The affected-version metadata is limited and somewhat inconsistent, so software inventory should confirm real installations.

Exploitation context

Sources identify public exploit material for file-format exploitation. However, exploitation requires local user interaction and the bundle does not support claims of active exploitation in the wild. Treat it as credible but mostly legacy risk.

Researcher notes

The CVE was published in 2025 for a 2009-era issue. Provided references include Metasploit, Exploit-DB, FortiGuard, VulnCheck, and an archived product site. No source in the bundle identifies a vendor patch, active exploitation, or broad modern deployment prevalence.

Mitigation direction

  • Inventory Windows endpoints for gAlan installations and .galan file associations.
  • Remove gAlan where it is not operationally required.
  • Block or quarantine untrusted .galan attachments and downloads.
  • Restrict file associations so .galan files do not auto-open in gAlan.
  • Check vendor or advisory guidance because no patch is named in the bundle.
  • Use endpoint monitoring for suspicious child processes from gAlan.

Validation and detection

  • Confirm whether gAlan 0.2.1 or earlier exists in software inventory.
  • Check endpoint telemetry for recent gAlan execution.
  • Review email and download controls for .galan file handling.
  • Verify EDR rules monitor file-format exploitation behavior.
  • If FortiGuard IPS is used, review coverage for signature 18034.
Prepared
Confidence
medium
Sources
9

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.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2009-20004 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
High
CVSS
8.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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.

1CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.4High
CVSS 4.0 vector shape for CVE-2009-20004Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gAlangAlan0unaffected
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.