From 702114479b53f0b708ad9835b834c0a24da4f490 Mon Sep 17 00:00:00 2001 From: Kyle ZENG Date: Wed, 15 May 2024 22:16:54 -0700 Subject: [PATCH] fix typo in house-of-tangerine --- glibc_2.31/house_of_tangerine.c | 2 +- glibc_2.32/house_of_tangerine.c | 2 +- glibc_2.33/house_of_tangerine.c | 2 +- glibc_2.34/house_of_tangerine.c | 2 +- glibc_2.35/house_of_tangerine.c | 2 +- glibc_2.36/house_of_tangerine.c | 2 +- glibc_2.37/house_of_tangerine.c | 2 +- glibc_2.38/house_of_tangerine.c | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/glibc_2.31/house_of_tangerine.c b/glibc_2.31/house_of_tangerine.c index 483d225..aaf8511 100644 --- a/glibc_2.31/house_of_tangerine.c +++ b/glibc_2.31/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.32/house_of_tangerine.c b/glibc_2.32/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.32/house_of_tangerine.c +++ b/glibc_2.32/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.33/house_of_tangerine.c b/glibc_2.33/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.33/house_of_tangerine.c +++ b/glibc_2.33/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.34/house_of_tangerine.c b/glibc_2.34/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.34/house_of_tangerine.c +++ b/glibc_2.34/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.35/house_of_tangerine.c b/glibc_2.35/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.35/house_of_tangerine.c +++ b/glibc_2.35/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.36/house_of_tangerine.c b/glibc_2.36/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.36/house_of_tangerine.c +++ b/glibc_2.36/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.37/house_of_tangerine.c b/glibc_2.37/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.37/house_of_tangerine.c +++ b/glibc_2.37/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() { diff --git a/glibc_2.38/house_of_tangerine.c b/glibc_2.38/house_of_tangerine.c index fe789a2..862a361 100644 --- a/glibc_2.38/house_of_tangerine.c +++ b/glibc_2.38/house_of_tangerine.c @@ -49,7 +49,7 @@ * *to make the PoC more reliable we need to malloc and probe the current top chunk size, * this should be predictable in an actual exploit and therefore, can be removed to get 5 malloc calls instead * - * Special Thanks to pepsipu for creating the challenge "High Frequency Trading" + * Special Thanks to pepsipu for creating the challenge "High Frequency Troubles" * from Pico CTF 2024 that inspired this exploitation technique */ int main() {