Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2004-1289: Buffer Overflow in pcal 4.7.1 getline and get_holiday Functions

Published Dec 22, 2004 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS14.7%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Pcal
IdentifiersCVE-2004-1289CWE-120

CVE-2004-1289 describes multiple buffer overflow vulnerabilities in pcal 4.7.1. Specifically, the vulnerabilities exist in the getline function in pcalutil.c and the get_holiday function in readfile.c. These functions do not properly validate the length of input data when processing calendar files, allowing an attacker to supply a specially crafted calendar file that triggers a buffer overflow.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the user running pcal, potentially leading to full system compromise if pcal is run with elevated privileges.

Mitigation

If you can’t patch tonight, do this now.

Do not process untrusted or unauthenticated calendar files with pcal. Restrict access to the application and monitor for suspicious calendar file submissions until a patch is applied.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of pcal where input validation and proper bounds checking have been implemented in the affected functions. If no official patch is available, apply custom patches to ensure all input buffers are properly bounded.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PcalPcalapplication
FAQ

Frequently asked questions

Is CVE-2004-1289 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2004-1289 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2004-1289?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2004-1289.
Is there a patch for CVE-2004-1289?
Upgrade to a patched version of pcal where input validation and proper bounds checking have been implemented in the affected functions. If no official patch is available, apply custom patches to ensure all input buffers are properly bounded.
What products are affected by CVE-2004-1289?
Pcal.
How severe is CVE-2004-1289?
CVE-2004-1289 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 14.7% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.