Memory Disclosure in Vignette StoryServer and Vignette V/5
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
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.
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.
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.
No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.