Codsmp.zip
Create and print IATA Air Waybills, manifests, dangerous goods declarations, labels, bills of lading. And create and transmit eAWBs/FWBs/Cargo-IMP messages.
Create and print IATA Air Waybills, manifests, dangerous goods declarations, labels, bills of lading. And create and transmit eAWBs/FWBs/Cargo-IMP messages.
AWB Editor is an easy to use program to create and print various air freight related documents. It can print AWBs both on pre-printed forms using a dot matrix printer and on blank paper using a laser printer. And also supports other documents such as manifests, dangerous goods declarations, barcoded labels and bills of lading.
Ready for the new times AWB Editor can create and transmit eAWB/FWB/Cargo-IMP messages. Electronic forms in AWB Editor are similar to the paper forms making the transition really easy.
Web AWB Editor is the latest version of AWB Editor that runs on web browsers; it requires no installation and it can be used from any computer where an internet connection is available.
You can try Web AWB Editor with a single click, without having to install anything or register.
You can register if you wish, this will make it possible to log in again and access your saved data and if you decide to start using the service you can do it with that account.
Web AWB Editor can be used in two modes:
* additional fees may apply, view fees for more details
The classic version of AWB Editor which runs as a standard desktop application, it is compatible with Windows, MacOS and Linux. It can run without access to the internet.
You can try AWB Editor and test all its features before deciding to purchase it. Download the installer, run it and AWB Editor will be ready to be used, no additional setup is required.
The desktop version fees are based on the number of workstations/installations from where the program is used. Fees starting at $150/year.
0x00001140 <main+40>: 1140: 48 8d 3d 0b 00 00 00 lea rdi,[rip+0xb] # 1152 <main+52> 1147: e8 34 ff ff ff call 1080 <puts@plt> 114c: b8 00 00 00 00 mov eax,0x0 1151: c3 ret
Both variations are often required for the “extra points” tier of a CTF. 4.2 Decrypting archive.enc The file size of archive.enc (≈5 KB) matches the size of payload.bin after XOR with a 6‑byte key, which suggests archive.enc may be the same data encrypted with a different key (maybe a rotating key). Let’s brute‑force the key length.
if __name__ == '__main__': main() Running it prints all four flags (the MD5/SHA‑256 ones will appear only if those derived binaries indeed contain a flag string). Adjust the extract_flag regex if the flag format differs. | Step | Tool / Command | What we learned | |------|----------------|-----------------| | 1️⃣ | file , unzip -l | Archive is not password‑protected; contains payload.bin , secret.py , archive.enc . | | 2️⃣ | Read `README codsmp.zip
Scope – This write‑up assumes you have obtained the codsmp.zip archive from a CTF or a reverse‑engineering challenge. The goal is to get the flag (or the hidden payload) that the archive is protecting. Prerequisites – A Linux/macOS workstation (or WSL on Windows) with the usual forensic / reverse‑engineering toolbox: unzip , 7z , binwalk , exiftool , strings , file , hexedit , john , hashcat , python3 , radare2 / ghidra , pwntools , etc. 1. Initial Inspection $ file codsmp.zip codsmp.zip: Zip archive data, at least v2.0 to extract, compressed size 1.3 MB, uncompressed size 5.6 MB, name=codsmp.zip
Inside this zip you will find a binary payload and a python script. The binary is encrypted with a custom XOR scheme. Your job is to recover the original binary and locate the flag. 0x00001140 <main+40>: 1140: 48 8d 3d 0b 00
Good luck! The README tells us that is XOR‑encrypted and that the script secret.py probably contains the key or the routine to decrypt it. 2.2 secret.py #!/usr/bin/env python3 import sys, itertools
$ strings -a payload_decrypted.bin | head -20 /lib64/ld-linux-x86-64.so.2 libc.so.6 GLIBC_2.2.5 puts printf ... if __name__ == '__main__': main() Running it prints
FLAGXOR_SINGLE_BYTE Now we have :