l1ackers

~/tutorials/046-when-you-find-something-real.md

046: When you find something real

Sooner or later the skills in this tier find a real bug in a real system somebody else owns. What happens next is a discipline, and the discipline is not optional equipment. It is the hat code, practiced as procedure.

The first hour

Verify it is real. Reproduce it twice from a clean state, then stop touching it. A finding you keep poking after confirming is a finding you are enjoying instead of handling, and every extra request is a decision you will explain later.

Write down the boundary you stayed inside. If you found it in a place with a published policy, quote the policy. If you found it somewhere with no policy, you were already off the road, and the honest writeup says so.

Then go quiet in the right way. No public posts, no screenshots, no telling the story until it is closed. Not because of etiquette. Because the clock has not started yet, and you control when it starts.

Finding where it goes

Before you can send anything, you have to find the address, and the field has built a machine-readable answer. Probe the two places a disclosure policy lives before you write a single word of the report:

$ curl -s https://example.com/.well-known/security.txt
$ curl -s https://example.com/security.txt

The first is the standard location, RFC 9116, and a site that ships it is telling you three things in plain lines: which address reports go to, what the policy's clocks are, and what they promise in return, the safe harbor sentence from lesson 045. The second URL is the legacy fallback from before the standard, and some sites still keep only that one. If both answer nothing, the policy hunt moves to the human places: the site's footer, its security page, the bug bounty directories, and the domain's registration contact as the last resort.

The honest live example, fired while writing this lesson: curl -s https://l1ackers.com/.well-known/security.txt answers nothing today. This site has no disclosure policy of its own yet, which is the kind of fact a site about disclosure should say out loud about itself, and the making of one is in the Try it below, aimed at the author as much as the reader.

The report

A vulnerability disclosure is the report shape from lesson forty-four, compressed and aimed at one reader. The affected system, exactly. The reproduction, numbered, from a clean machine. The impact, in their vocabulary not yours. A fix if you can see one. What you did and did not touch, do, and access.

The field has settled formats: a markdown security advisory on a repository, a page under the vendor's own security directory, an email to the address in their policy. Use their format. Read their policy first, because it has clocks in it.

The clocks

Most policies promise a fixed window, commonly 90 days, from report to public. The bargain is symmetrical. You hold the details private while they work. They work, because at the end of the window the finding publishes whether or not the fix shipped.

Ninety days is not sentiment. It is the number that keeps both sides honest, and it was fought for. Honor it, extend it for good faith, and never let silence be the reason something publishes.

When they do not answer

It happens. The address bounces, the ticket closes itself, the vendor's reply is a lawyer.

The escalation ladder exists and it is boring on purpose. Try a second channel. Try a coordinator, a CERT or your national CSIRT, whose entire job is holding a finding between two parties who are not talking. Only the public route ends the ladder, and the decision to walk it belongs to the calmest version of you, weeks after the anger, if anger ever showed up.

This site practices it

The news files in this tree are disclosure reports, one per finding, each with its primary source in the frontmatter:

grep source: ~/news/2026-09-21-panos-globalprotect-cookie-auth-bypass.md
source: https://security.paloaltonetworks.com/CVE-2026-0257

Every item cites where the finding came from, never a summary of a summary. That rule is the disclosure habit in miniature: the primary source is the receipt.

The tier, closed

This is where the road that started at a shell on somebody else's site ends: holding a real finding, in a real system, and doing the right thing with it because you practiced the right thing when nothing was at stake. The fifteen lessons before this one handed you the tools one at a time. This one hands you the code that decides what the tools are for.

Count what exists, the way this site always counts. The answer is 63 as this is written, and the command to check it is one line below:

ls ~/tutorials | wc -l
63

<!-- claim: 63 = ls ~/tutorials | wc -l -->

Three tiers, three rooms. First Steps taught the shell on a site that answers. Field Work taught judgment inside a jail that is honest about its limits. Live Fire taught the real tools, on your own iron, where nobody checks your output but you. Through all three, one rule never moved: the question before every command is whose machine it lands on.

The shell at the bottom of the page is still there, and the tree still goes deeper than the part you can see. Nothing here is finished, and neither are you. That is not a flaw in the ending. It is the design of the machine you started on, and now you run one of your own.

Try it

  1. Read three disclosure reports from the news tree. Note which parts carry the weight: reproduction, impact, timeline.
  2. Write one practice disclosure for a bug you planted in your own lab. Full shape, aimed at an imaginary vendor. The whole letter is behind the reveal below, and stealing its shape is what it is there for.
  3. Probe five real sites for security.txt. Count how many answer. That ratio, gathered with two curl commands, is a fact about the industry's disclosure posture you now know firsthand.
  4. Keep your practice letter. The first real one will arrive with no warning, and it will be better for having a shape to fall back on.
Reveal the answer

The disclosure email, whole, the shape to steal. Written for a planted lab bug, aimed at an imaginary vendor, every section doing the job its name claims:

To: [email protected]
Subject: SQL injection in the login form of shop.example-vendor.test

Hello security team,

While testing a lab deployment of ShopServer 2.4.1, the current stable
download, I found a SQL injection in the login form. I am reporting it
here because your security.txt lists this address and asks for reports
in this window. Everything below happened on my own machines.

THE AFFECTED SYSTEM, EXACTLY

  ShopServer 2.4.1, the current stable download from your site, default
  configuration, running on Ubuntu 24.04 with the bundled PHP 8.3. The
  page is /login, the form field is named username, and the behavior is
  present with no plugins or themes installed beyond the defaults.

THE REPRODUCTION, NUMBERED, FROM A CLEAN MACHINE

  1. Install ShopServer 2.4.1 from your download, default settings.
  2. Open the login page, /login.
  3. Enter anything as the password.
  4. Enter this as the username:

     ' OR '1'='1' --

  5. Submit. The response is a redirect to the account page, logged in
     as the first account in the database.

  The injection works because the username is concatenated into the
  query unescaped. The two dashes comment out the password check. The
  result is authentication as the first row the query returns.

THE IMPACT, IN YOUR VOCABULARY

  A remote attacker with no credentials becomes the first account in
  the database. On a default install that is the administrator. No
  special configuration is required, and the request leaves one line in
  the access log, an ordinary POST to /login.

WHAT I DID AND DID NOT DO

  I logged in three times, on two installs, from one address. I read
  the account page and logged out. I did not enumerate other accounts,
  download the database, change any data, access any other page as the
  injected session, or test anything beyond the login form. My notes
  and the two virtual machines are available if they help you.

A FIX, IF IT HELPS

  The username and password appear to be concatenated into the SQL
  query. Parameterized queries close this class at the login form, and
  the same pattern may exist wherever the code builds a query from form
  input, which is why I am reporting the class and not only this field.

  A temporary mitigation that breaks nothing I could see: reject
  usernames longer than 64 characters at the login form.

COORDINATION

  I will hold every detail private for 90 days from your
  acknowledgment, and longer if you are working on it and ask. I will
  not publish without telling you first. If the window needs extending,
  say so and it extends. If I hear nothing in 14 days I will resend
  once to this address and try one other channel, in that order.

  You can reach me at this address, and I will answer within a day.

                                          (name, or a handle, one line)

Read it back the way the vendor will. The subject line names the bug, the system, and the site, so the triage person files it in one glance. The first paragraph answers the three questions they must ask before reading further: what, where, and why this address, with the security.txt receipt doing the third. The reproduction is numbered and stranger-runnable, the same discipline as lesson 044, because a report they cannot reproduce is a report they close. The impact section is three sentences, no adjectives, and the middle sentence is the one that moves: on a default install that is the administrator. The did-not-do section is the trust engine of the whole letter, volunteering the boundary without being asked. The fix names the class. And the coordination section is the clocks from this lesson, in writing, with your promises on one side only, which is all you control.

Two notes on sending. Plain text, no attachments unless they ask, because attachments die in mail gates and pastebin links die in trust. And send it from an address you will still control in ninety days, because the reply you are waiting for has a way of arriving on day eighty.

l1ackers · shell this is a way in, not a requirement
$