Linux Labs

Server security / Stage 2 of 10

The update is in, the vulnerability is still alive

Not running Starting usually ~20 s
Leave the lesson

Step 5 of 7 · on a machine · 5 min

Data gets stale too

A service holds open more than its program and libraries. Address lists, certificates and signature databases are also upgraded by packages.

lab-guard tells the shop whether to let in a client with a given address: allow or deny. The list of blocked addresses comes in a separate package, lab-guard-rules. Last night it was upgraded: 203.0.113.7, the source of a password brute force, was added to the list. After the upgrade needrestart did not name lab-guard.

Exercise · do it

Apply the new address list

lab-guard still lets through an address from the upgraded list: curl -s 'http://127.0.0.1:8091/check?ip=203.0.113.7' prints allow. Make the service apply the new list.

Sign in and start The machine is available after signing in

Goals · 0 of 2

  • Deny access to 203.0.113.7 not done yet
  • Keep lab-guard running and free of deleted files not done yet

Step goals

0 of 2
  • Deny access to 203.0.113.7 — not done yet
  • Keep lab-guard running and free of deleted files — not done yet
Ubuntu 24.04

Step goals

0 of 2
  • Deny access to 203.0.113.7 — not done yet
  • Keep lab-guard running and free of deleted files — not done yet
Loading…