VMime through 0.9.2 Uninitialized Stack Memory Disclosure via uuencode Decoder
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VMime, a C++ mail handling library, is affected, and an attacker who sends a specially crafted uuencoded email attachment can cause the library to leak small amounts of uninitialized memory from the program's stack into decoded attachment data. This could expose fragments of sensitive in-memory information to whoever receives or processes the decoded output.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
VMime through 0.9.2 contains an information disclosure vulnerability in the uuEncoder::decode function that writes uninitialized stack memory into decoded output for over-long lines. Attackers can send a crafted uuencode or x-uuencode MIME part with a large line length byte to leak up to 15 bytes of stack contents per line in decoded attachments.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kisli vmime
through 0.9.2