🎯 Rust Fixme 3
A detailed write-up of the Misc challenge 'Rust Fixme 3' from PicoCTF - 2025
📊 Challenge Overview
Category Details Additional Info 🏆 Event PicoCTF - 2025 Event Link 🔰 Category Misc 🎯 💎 Points 100 Out of 500 total ⭐ Difficulty 🟢 Easy Personal Rating: 1/10 👤 Author Taylor McCampbell Profile 🎮 Solves (At the time of flag submission) 2.661 solve rate 📅 Date 15-03-2025 PicoCTF - 2025 🦾 Solved By mH4ck3r0n3 Team:
📝 Challenge Information
Have you heard of Rust? Fix the syntax errors in this Rust file to print the flag! Download the Rust code here.
🎯 Challenge Files & Infrastructure
Provided Files
Files:
🔍 Initial Analysis
First Steps
This is the third challenge in the
Rust Fixme
series. The comments in this challenge are:
// Did you know you have to do "unsafe" operations in Rust?
As we can imagine, this introduces the use of Rust’s “unsafe” for operations that directly manipulate pointers. Let’s move on to the next phase.
🎯 Solution Path
Exploitation Steps
Exploitation
The first thing I did was uncomment the
unsafe
block, as it needs to be uncommented to execute it. Then, inside theunsafe
block, I kept the code that manipulates raw pointers and created a slice usingstd::slice::from_raw_parts
to get the content of the decrypted buffer. After running the program, I obtained the flag.
🛠️ Exploitation Process
Approach
Since I’ve already explained the fixes made, I’ll just leave the file with the modifications here:
🚩 Flag Capture
FlagpicoCTF{n0w_y0uv3_f1x3d_1h3m_411}
Proof of Execution
🔧 Tools Used
Tool Purpose Rust Exploit
💡 Key Learnings
Skills Improved
- Binary Exploitation
- Reverse Engineering
- Web Exploitation
- Cryptography
- Forensics
- OSINT
- Miscellaneous
📚 References & Resources
Similar Challenges
Learning Resources
📊 Final Statistics
Metric | Value | Notes |
---|---|---|
Time to Solve | 00:08 | From start to flag |
Global Ranking (At the time of flag submission) | 1175/10517 | Challenge ranking |
Points Earned | 100 | Team contribution |
Created: 15-03-2025 • Last Modified: 15-03-2025 *Author: mH4ck3r0n3 • Team: *