DetectLog4j blue team ctf
Category : Digital Forensics
1293 Players
4.3
(118)
Medium
-
Weight : 50 | Solved : 594
-
Weight : 50 | Solved : 535
-
Weight : 50 | Solved : 518
-
Weight : 50 | Solved : 518
-
Weight : 50 | Solved : 512
-
Weight : 50 | Solved : 466
-
Weight : 50 | Solved : 460
-
Weight : 50 | Solved : 480
-
Weight : 100 | Solved : 459
-
Weight : 100 | Solved : 443
-
Weight : 50 | Solved : 372
-
Weight : 50 | Solved : 362
-
Weight : 100 | Solved : 347
-
Weight : 100 | Solved : 356
-
Weight : 200 | Solved : 308
-
Weight : 50 | Solved : 324
-
Weight : 50 | Solved : 313
-
Weight : 50 | Solved : 319
-
Weight : 100 | Solved : 286
-
Weight : 150 | Solved : 285
-
Weight : 150 | Solved : 274
-
Weight : 50 | Solved : 273
-
Weight : 100 | Solved : 253
-
Weight : 100 | Solved : 260
Instructions:
- Uncompress the challenge (pass: cyberdefenders.org)
Scenario
For the last week, log4shell vulnerability has been gaining much attention not for its ability to execute arbitrary commands on the vulnerable system but for the wide range of products that depend on the log4j library. Many of them are not known till now. We created a challenge to test your ability as a soc analyst to detect, analyze, mitigate and patch products vulnerable to log4shell.
Tools:
WriteUps
Submit Writeup-
SHA1SUM:6556e7d46e89bf2ea68e05cf101920e2de071a22
-
Password:cyberdefenders.org
-
Size:2.8 GB
-
Published:Jan. 15, 2022, midnight
Authors