From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Michael William Jonathan <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>
Subject: Re: CF ticketing system is still vulnerable
Date: Sat, 22 Apr 2023 06:21:17 +0700 [thread overview]
Message-ID: <CAFBCWQLN3ZTDciA+K4APQcR9XjJm8v_wec8BNiEe5swa3gRv-A@mail.gmail.com> (raw)
In-Reply-To: <CAFBCWQL2i53P7QwHRXFu8WFbFbC7G8rLi-nNqqzRdeaXTC7F-g@mail.gmail.com>
On Fri, Apr 21, 2023 at 7:45 AM Ammar Faizi wrote:
> On Fri, Apr 21, 2023 at 7:42 AM Alviro Iskandar Setiawan wrote:
> > POC and sample attached.
> >
> > gcc -Wall -Wextra -O2 -ggdb3 gwcfd2.c -o gwcfd2 -lcurl -ljson-c -lpthread;
> > ./gwcfd2;
>
> I'll address this ASAP.
I sent your POC and sample to the KiosTix people yesterday. At first,
they didn't acknowledge the leak because they thought you leaked the
old tickets.
Looking at their response, they will need a few days to mull things
over before they fix the vuln. Plus, they will probably have
difficulty grasping what your crazy multithreaded POC is actually
doing. So let's give them more time; they're web developers, not
super-savants.
--
Ammar Faizi
next prev parent reply other threads:[~2023-04-21 23:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOG64qN7ZPE+twkvxWM8uq4NDsWzbUsXGYvrPxhf55YWG2G3Ww@mail.gmail.com>
2023-04-21 0:45 ` CF ticketing system is still vulnerable Ammar Faizi
2023-04-21 23:21 ` Ammar Faizi [this message]
2023-04-21 23:41 ` Alviro Iskandar Setiawan
2023-04-21 23:50 ` Ammar Faizi
2023-04-22 0:09 ` Alviro Iskandar Setiawan
2023-04-22 0:18 ` Ammar Faizi
2023-04-22 0:29 ` Alviro Iskandar Setiawan
2023-04-22 0:41 ` Ammar Faizi
2023-04-22 0:54 ` Alviro Iskandar Setiawan
2023-04-22 1:01 ` Ammar Faizi
2023-04-22 2:35 ` Ammar Faizi
2023-04-22 6:02 ` Alviro Iskandar Setiawan
2023-04-22 6:38 ` Ammar Faizi
2023-04-22 6:53 ` Alviro Iskandar Setiawan
2023-04-22 7:49 ` Telegram bot? (was: Re: CF ticketing system is still vulnerable) Ammar Faizi
2023-04-22 7:52 ` Alviro Iskandar Setiawan
2023-04-22 7:59 ` Ammar Faizi
2023-04-22 8:00 ` Alviro Iskandar Setiawan
2023-04-22 22:58 ` CF ticketing system is still vulnerable Alviro Iskandar Setiawan
2023-04-22 23:06 ` Ammar Faizi
2023-04-22 23:11 ` Alviro Iskandar Setiawan
2023-04-22 23:23 ` Alviro Iskandar Setiawan
2023-04-22 23:36 ` Ammar Faizi
2023-04-23 1:28 ` Alviro Iskandar Setiawan
2023-04-23 1:31 ` Alviro Iskandar Setiawan
2023-04-23 1:38 ` Ammar Faizi
2023-04-23 1:47 ` Alviro Iskandar Setiawan
2023-04-23 1:53 ` Ammar Faizi
2023-04-23 3:33 ` Alviro Iskandar Setiawan
2023-04-23 3:36 ` Ammar Faizi
2023-04-23 3:48 ` Moe
2023-04-23 3:56 ` Ammar Faizi
2023-04-23 5:23 ` Alviro Iskandar Setiawan
2023-04-23 5:28 ` Ammar Faizi
2023-04-23 5:43 ` Alviro Iskandar Setiawan
2023-04-23 5:35 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFBCWQLN3ZTDciA+K4APQcR9XjJm8v_wec8BNiEe5swa3gRv-A@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox