public inbox for [email protected]
 help / color / mirror / Atom feed
From: Louvian Lyndal <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Michael William Jonathan <[email protected]>,
	 "GNU/Weeb Mailing List" <[email protected]>
Subject: Re: gwcfd v3
Date: Tue, 22 Oct 2024 06:10:07 +0700	[thread overview]
Message-ID: <CAP2ubg+WYnARBEqy7eG7M7dFDpZxKrbYA5VC2ZnX1G94GpqQ4Q@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qNm7kWQ829B-5jWZdVHWj=ypzgFgmS1F3KZp3rnMKYfPw@mail.gmail.com>

On Tue, Oct 22, 2024 at 5:30 AM Alviro Iskandar Setiawan wrote:
> On Tue, Oct 22, 2024 at 4:57 AM Louvian Lyndal wrote:
> > I even included a sample URL that anyone could access without login,
> > but apparently, that's just how they like it-wide open and welcoming
> > to all.
>
> Can you give me a sample or the dump file?

You can find a BTB here:
http://dzi6vje7g62egwengyit3p42qp5a7xvgtivgplphpgykbz5ahc2sxcad.onion/

> How far does the vulnerability give you access to their system?

At worst, it's just dumping the tickets, but then we can extract the
user info from the invoice.

And didn't I mention the XML endpoint. That's where the magic happens.
It's like a buffet for file listings, just sitting there, waiting to
be harvested. That's the crown jewel of the whole operation if you
want to dump everything.

It's absolutely baffling that this vulnerability even exists in the
first place. It's not just a slip-up; it's a glaring oversight that
shouldn't happen in any serious system. Leaving something like this
wide open is basically inviting trouble-it's not just careless, it's
downright irresponsible.

      reply	other threads:[~2024-10-21 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 21:57 gwcfd v3 Louvian Lyndal
2024-10-21 22:29 ` Alviro Iskandar Setiawan
2024-10-21 23:10   ` Louvian Lyndal [this message]

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=CAP2ubg+WYnARBEqy7eG7M7dFDpZxKrbYA5VC2ZnX1G94GpqQ4Q@mail.gmail.com \
    [email protected] \
    [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