Semu i megghiu
| Service name | Port | Flag description | Language | Exploit | Patch |
|---|---|---|---|---|---|
| pirate_map | 20038 | Flags are indentified by treasure name. | bin | ✅ | ❌ |
| hanoiFones | 20040 | Flags are identified by the auction IDs. | bin | ✅ | ❌ |
| red_messenger | 20064 | The flag ID is the name of the user who send to himself a message with the flag in it. | C | ✅ | ❌ |
| sharing | 20065 | Flags are identified by the sharing key | Python / DB | ❌ | ❌ |
| Bl4ckG0ld | 20066 | Flags are identified by the RecipeNo. | bin | ❌ | ❌ |
| nadmozg | 20067 | private dictionary name | C/bin | ✅ | ❌ |
| FHM-Maintenance | 20111 | Flags are identified by the username. | / | ✅ | ❌ |
| ropeman | 20129 | Flags are identified by the note name.The flags are the status field in a txt file for a registered user | bin | ✅ | ❌ |
| hacker_diary | 20130 | A flag_id is an entry id which corresponds to a detailed, prehashed description of an exploit. http: //: /entries/<flag_id> should yield an entry with the flag | Python/Django | ✅ | ✅ |