| Field | Detail |
|---|---|
| Platform | TryHackMe |
| Room URL | tryhackme.com/room/systemsattackvectors |
| Category | SOC / Blue Team |
| Status | ✅ Completed |
| Points Earned | — |
| Tasks Completed | 7 |
| GitHub File | labs/tryhackme/rooms/systems-as-attack-vectors.md |
| Live Website | tryhackme.html |
Learn how attackers exploit vulnerable and misconfigured systems, and how you can protect them. The room covers system-based attack vectors that bypass the human layer entirely, including software vulnerabilities (CVEs), misconfigurations, and supply chain attacks, and how SOC analysts and IT teams respond to each.
Worked through each task sequentially, distinguishing between the three primary system attack routes. Applied the key distinction between vulnerabilities and misconfigurations, then engaged with the interactive security dashboard to make live analyst decisions on systems at risk and build a remediation plan.
Three system attack routes:
| Route | How it works | Example |
|---|---|---|
| Human-led | Users inadvertently open the door — weak passwords, USB drops, pirated software | 81% of breaches involve stolen or weak passwords |
| Vulnerabilities (CVEs) | Security flaws in software, sometimes undiscovered for years | Shellshock: existed since 1992, discovered 2014 |
| Supply chain | Malware injected into a trusted app or library, pushed to all users via update | SolarWinds, 3CX breaches |
Vulnerability vs Misconfiguration — critical distinction:
| Type | What it is | How to fix |
|---|---|---|
| Vulnerability | A bug in the software code | Patch (software update from vendor) |
| Misconfiguration | A setup error made by the IT team | Reconfiguration, a patch does NOT fix this |