l1ackers
Not marked. Sign in and it follows you. Next: 045: Rules of engagement

~/tutorials/044-the-deliverable.md

044: The deliverable

Everything in this tier ends in the same artifact. Not a shell, not a flag, not a story. A document a stranger can act on. Lesson twenty-five built the finding shape inside the jail. Here is the whole report.

The report is the only part of an engagement the client's whole organization sees. The exploit impressed one engineer. The report moves budgets.

The parts

Executive summary. One page. What was tested, what was found, in the client's vocabulary. Written last, read first, and the only page most of the audience will open.

Findings. Each one the four fields from lesson twenty-five, and the discipline is unchanged:

cat ~/tutorials/025-the-report-shape.md | head -40

What. Where. Evidence. So what. A finding without the evidence is an opinion, and a finding without the so what is homework.

Reproduction. Numbered steps a stranger runs, from a clean machine, and gets what you got. This is the part that proves the work, and the part that survives you. Six months later the fix gets questioned, and the reproduction is the answer.

Fix. Specific. Not harden the server. The line to change, the setting to set, and what breaks when it is set. A fix section that ignores the breaking is a fix that quietly never happens.

Severity, ranked honestly. Ranked by the client's risk, not your pride. The boring misconfiguration that owns the domain outranks the exotic memory corruption you enjoyed more, and the report that ranks by enjoyment gets treated, correctly, as entertainment.

A whole report, from a real lab

The best way to teach the shape is to fill one in. The lab is the misconfigured Ubuntu from lesson 036, two findings, both planted then found the way a real assessment finds them, by reading the census honestly. Here is the whole report for it, every line of evidence pasted as the lab printed it.

The executive summary.

> A security review of one lab host found two misconfigurations, both allowing a standard user to execute commands as root. Both were confirmed by demonstration, closed by one-line configuration changes each, and verified closed from the user account after fixing. No software was patched and none needed to be. These are configuration errors, and the fixes are configuration lines.

Findings one and two, the four fields each.

> Finding 1. A sudo rule grants passwordless find, which executes arbitrary commands as root. > > What: The user student may run /usr/bin/find as root without a password. find's -exec action runs any command it is given, with find's own privileges. > > Where: /etc/sudoers.d/student, the host from lesson 036's lab. > > Evidence: sudo -l as student answers (root) NOPASSWD: /usr/bin/find, and sudo find /etc -name hostname -exec id \; answers uid=0(root) gid=0(root) groups=0(root). > > So what: Any user who can become student, including student, is root on this host. The command is not find in any meaningful sense, because -exec is a documented, intended feature, and the sudo rule grants the whole binary.

> Finding 2. A root cron entry runs a script writable by every user. > > What: /opt/scripts/backup.sh runs as root every five minutes and carries mode 777, world writable. > > Where: /etc/cron.d/backup and /opt/scripts/backup.sh. > > Evidence: ls -la reads -rwxrwxrwx 1 root root 12 ... /opt/scripts/backup.sh and the cron entry reads */5 root /opt/scripts/backup.sh. > > So what: Any user on the host can append to a script root executes on a schedule. Lesson 036 demonstrated the full chain: one appended line, one copy of bash marked setuid, root on the next tick.

Reproduction, numbered, a stranger's hands.

> 1. Open a shell on the host as the standard user. > 2. Run sudo -l. Confirm the output line (root) NOPASSWD: /usr/bin/find. > 3. Run sudo find /etc -name hostname -exec id \;. Confirm the output begins uid=0(root). > 4. Run ls -la /opt/scripts/backup.sh. Confirm the mode begins -rwxrwxrwx. > 5. Run cat /etc/cron.d/backup. Confirm the entry runs the script as root on a five minute schedule.

Step 2 and 3 reproduce finding 1 in one minute. Steps 4 and 5 reproduce finding 2's precondition, and lesson 036's reveal carries the rest of that chain, deliberately not repeated here, because a report references its evidence and a tutorial hands over its means.

The fix section, both lines, and what each breaks.

> Finding 1: delete /etc/sudoers.d/student. Nothing legitimate breaks, because nothing should rely on passwordless find. If a workflow genuinely needs scheduled find, grant the specific command line, not the binary. > > Finding 2: chmod 644 /opt/scripts/backup.sh. The cron entry continues to run unchanged, because root's own execution never needed the write bit. What breaks is convenience: whoever was editing that script without sudo now needs sudo, which is the correct state.

And the close, verified from the seat the findings lived in, which is the part most reports skip and the part that makes this one credible:

> After both fixes, from the student account: sudo -n -l answers sudo: a password is required, and appending to the script answers Permission denied. Both findings are closed and demonstrated closed, not declared closed.

Severity, ranked. Both findings are the same severity, full privilege escalation for a standard local user, and honesty here means saying so plainly instead of manufacturing a ranking. The order in the report is by fix cost, cheapest first, which is also the order the client should fix them in, and a report that quietly ranks by ease-of- fix is doing the client's planning for them without saying so.

The voice

The same rule this site runs on. Write what you did, write what came back, write what it means. No adjectives doing the work of evidence, no critical doing the work of inconvenient, and no finding you cannot reproduce on request.

Notice what the report above never says. No devastating, no trivially exploited, no attacker could. Every claim is a sentence next to the command that proves it, and the two findings that read plainest are the two a client can act on fastest. The client does not pay for the exploit. They pay for the sentence that makes the fix obvious.

Try it

  1. Attack your own lab for one hour. Anything you find. The 036 lab is a fair target, or plant your own.
  2. Write the report. All the parts. One evening is enough for a two finding report and it will be the hardest evening of this tier.
  3. Close what you found, verify the close from the user's seat, and put the verification in the report. A finding that ends at the fix is half a finding.
  4. Hand it to somebody who did not watch you work. Ask them one question: what would you do first? If the answer is not your top finding, the report failed, and now you know why.
Not marked. Sign in and it follows you. Next: 045: Rules of engagement
l1ackers · shell this is a way in, not a requirement
$