Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2003-0400: Memory Disclosure in Vignette StoryServer and Vignette V/5

Published Jun 11, 2003 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS3.5%89th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Vignette
IdentifiersCVE-2003-0400CWE-125

Vignette StoryServer and Vignette V/5 incorrectly calculate the size of text variables, causing responses to include unauthorized portions of memory. The issue can be triggered by supplying the string "-->" in the CookieName argument to the login template. Although sometimes described as a "memory leak," this vulnerability discloses memory contents rather than exhausting memory through unreleased allocations.

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.

The vulnerability compromises confidentiality by exposing portions of application memory to a requester. Disclosed data may contain sensitive information, depending on the memory contents at the time of exploitation. The specific information exposed and the extent of disclosure are not established.

Mitigation

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

Limit exposure by restricting access to the login template, monitoring for suspicious input patterns (such as unusual CookieName values), and employing web application firewalls to block malicious requests. Regularly review and sanitize user-supplied input to templates.

Remediation

Patch, then assume compromise.

Apply vendor-supplied patches or updates that address the improper memory handling in text variable size calculation. If no patch is available, restrict access to the affected templates and sanitize user input to prevent exploitation.

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
VignetteContent Suiteapplication
VignetteStoryserverapplication
VignetteVignetteapplication
FAQ

Frequently asked questions

Is CVE-2003-0400 exploited in the wild?
As of Oct 22, 2026, Mallory has no reports of CVE-2003-0400 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2003-0400?
Yes. As of Oct 22, 2026, Mallory has reports of a public exploit for CVE-2003-0400.
Is there a patch for CVE-2003-0400?
Apply vendor-supplied patches or updates that address the improper memory handling in text variable size calculation. If no patch is available, restrict access to the affected templates and sanitize user input to prevent exploitation.
What products are affected by CVE-2003-0400?
Vignette Storyserver, Vignette, and Vignette Content Suite.
How severe is CVE-2003-0400?
CVE-2003-0400 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 3.5% (89th percentile) as of Oct 22, 2026.
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.