sophie🧟‍♀️

Vulnerability Research and other InfoSec things ☕️ My views are my own 🎆 @[email protected]

[sophie🧟‍♀️ @misosoupysan]

Just completed my blog post on source code auditing to windows privesc via Use After Free on HackSysExtremeVulnerableDriver! https://t.co/7PdOxOiKrY

[sophie🧟‍♀️ @misosoupysan]

https://t.co/u6KxYN26OW

[sophie🧟‍♀️ @misosoupysan]

@sc0p3r Looks awesome! I'll take a look

[d0nut 🦀 @d0nutptr]

This is absolutely insane

https://t.co/IEdMUHErX2

[0xor0ne @0xor0ne]

Linux kernel exploitation series.
A must read!
Credits @_lkmidas

Part 1: https://t.co/abiqJ0rleT
Part 2: https://t.co/DUN5nwEAI0
Part 3: https://t.co/bpYaC6DiJQ

#Linux #kernel #exploit #informationsecurity #cybersecurity

[sophie🧟‍♀️ @misosoupysan]

@fir3xfly I had actually never heard of the term quine before until now 😅 Nice blogpost!

[L0phtCraic @fir3xfly]

I took a break from writing my thesis this weekend and wrote about self replicating programs instead: https://t.co/jHm4X8Iep4

[sophie🧟‍♀️ @misosoupysan]

@ex_raritas Attempting the challenges between watching spooky movies 🎃

[chompie @chompie1337]

Curious about exploiting VMs or memory bugs in a safe language? Read my new blog post, where I attack Firecracker, AWS' VMM written in Rust. Learn about the various layers of virtualization + the attack surface, and how design decisions impact security.
https://t.co/FNN7JjeRce

[Gabriele Corno @Gabriele_Corno]

Deer Lounge Under Cherry Blossom Trees In Japan's Nara Park

[sophie🧟‍♀️ @misosoupysan]

@b10tt0 But yeah I think it's a good question for people who sort of have a basic foundation of Rust memory management and smart pointers already

[sophie🧟‍♀️ @misosoupysan]

@b10tt0 Yeah I think that it's a good question! It was fun to read up on smart pointers and the interior mutability pattern, though I think that using Rc and RefCell together off the bat could maybe be tough for people who are just starting to learn Rust

[sophie🧟‍♀️ @misosoupysan]

@b10tt0 Yeah I read about interior mutability a while ago but had to completely relearn it all to produce this code snippet 🥲

[sophie🧟‍♀️ @misosoupysan]

@b10tt0 With [*] containing the same format string a = {} and b = {}. Sorry I couldn't fit it all into one tweet. It also took me ages to figure out

[sophie🧟‍♀️ @misosoupysan]

@b10tt0 use core::cell::RefCell;
use std::rc::Rc;

fn main() {
let a = Rc::new(RefCell::new(2));
let b = Rc::clone(&a);

println!("\n\nstart: a = {} and b = {}\n", a.borrow(), b.borrow());
*a.borrow_mut() += 1;
println!("++a\nend: [*]\n\n", a.borrow(), b.borrow());
}

[sophie🧟‍♀️ @misosoupysan]

@fir3xfly Thank you!

[sophie🧟‍♀️ @misosoupysan]

Found out today that I graduated from uni with a first class honours, and with a first for my dissertation!🥳

[sophie🧟‍♀️ @misosoupysan]

@0x68306767 Thank you!

[sophie🧟‍♀️ @misosoupysan]

@ElementalX2 Thank you so much!

[sophie🧟‍♀️ @misosoupysan]

Big thanks to the markers who ignored the typo in my abstract🍻

[Battle Programmer Yuu @netspooky]

This is the finished product, I ended up keeping it simple because this was already a huge tangent to explain the context and significance of Linear Executables for this writeup on a bug for #BGGP3 https://t.co/yBz6rGP73i