한국어
English Indonesia Türkçe Deutsch Español Português Pусский Français Italiano Nederlands Polski العربية ไทย Tiếng Việt 繁體中文 简体中文 日本語 한국어

#34c3ctf 검색 결과

"#34c3ctf"에 대한 결과가 없습니다
_niklasb's profile picture. research @dfsec_com - @niklasb@infosec.exchange
Niklas B
 @_niklasb
2018. 3. 25.

phoenhex.re/2018-03-25/not… is about a cool feature of Vagrant that allows unprivileged guest processes to read/write the entire host filesystem. If you do not like this feature in your Vagrant setup, export VAGRANT_DISABLE_VBOXSYMLINKCREATE=1 Also, babyvm2 writeup for #34c3ctf

1
74
135
3
0
LiveOverflow's profile picture. wannabe hacker... he/him 🌱 grow your hacking skills @hextreeio
LiveOverflow 🔴
@LiveOverflow
2018. 3. 16.

software_update challenge from the #34c3ctf was an awesome practical example of math applied to security. We learn about basic linear algebra and finite-fields to break an XOR signature implementation. youtube.com/watch?v=EOlddN…

LiveOverflow's tweet card. Linear independence and GF(2) - 34C3 CTF software_update (crypto)...

youtube.com

YouTube

Linear independence and GF(2) - 34C3 CTF software_update (crypto)...

출처: youtube.com
2
15
72
1
0
ioc_feed's profile picture. #malware #infosec #ioc For now, I'm just retweeting Twitter accounts known to share IOCs. Will make this smarter when I have some free time 😀
IOC Feed
 @ioc_feed
2018. 3. 10.

RT hasherezade "RT LiveOverflow: Part 1/2 of another #34c3ctf challenge. The solution of this one really blew me away. But in the first episode we just review the code and think of possible attacks. youtube.com/watch?v=Vgdhlh…"

0
0
0
0
0
LiveOverflow's profile picture. wannabe hacker... he/him 🌱 grow your hacking skills @hextreeio
LiveOverflow 🔴
@LiveOverflow
2018. 3. 9.

Part 1/2 of another #34c3ctf challenge. The solution of this one really blew me away. But in the first episode we just review the code and think of possible attacks. youtube.com/watch?v=Vgdhlh…

LiveOverflow's tweet card. Python code audit of a firmware update - 34C3 CTF software_update...

youtube.com

YouTube

Python code audit of a firmware update - 34C3 CTF software_update...

출처: youtube.com
2
8
58
1
0
ioc_feed's profile picture. #malware #infosec #ioc For now, I'm just retweeting Twitter accounts known to share IOCs. Will make this smarter when I have some free time 😀
IOC Feed
 @ioc_feed
2018. 3. 2.

RT hasherezade "RT LiveOverflow: Two years ago I failed to solve the pwnable readme challenge at the #32c3ctf. Since then I have learned a lot and I got another chance at the #34c3ctf! youtube.com/watch?v=lE6ke7…"

0
0
0
0
0
_tsuro's profile picture. @v8js security, CTFs and CPU vulnz. LCHL. @tsuro@infosec.exchange
stephen
 @_tsuro
2018. 2. 21.

This is the best writeups on advanced heap exploitation I've read in a while. I think technique 1 is what @maciekkotowicz used in #34c3ctf.

Friz_N's profile picture. Security Researcher
frizn
 @Friz_N
2018. 2. 21.

From heap to RIP: getting code execution from pure glibc heap mechanics blog.frizn.fr/glibc/glibc-he…

3
183
340
7
0
0
5
18
0
0
_niklasb's profile picture. research @dfsec_com - @niklasb@infosec.exchange
Niklas B
 @_niklasb
2018. 2. 12.

This is essentially the babyvm2 challenge from #34c3ctf. Will do a writeup maybe after my next exam :)

0
0
10
0
0
_niklasb's profile picture. research @dfsec_com - @niklasb@infosec.exchange
Niklas B
 @_niklasb
2018. 1. 17.

CVE-2018-2693 was my intended solution for babvm2 at #34c3ctf, which DragonSector also found. It allows (amongst others) access to shared folders from unprivileged processes, so we can create symlinks and open them host-side. May do a writeup if valis won't.

1
10
34
1
0
SIGFLAG_CTF's profile picture. CTF Team of @jkulinz
SIGFLAG
 @SIGFLAG_CTF
2018. 1. 12.

We are proud to share our first ever blog post with you. Many thanks to @koyaan5 for explaining us how to solve the m0rph challenge from #34C3CTF sigflag.at/blog/2017/writ…

0
2
6
0
0
koyaan5's profile picture. I dabble in things
armin weihbold
 @koyaan5
2018. 1. 12.

My beginner focused writeup of solving the morph challenge from #34C3CTF with @radareorg I did for @SIGFLAG_CTF was just published! sigflag.at/blog/2017/writ…

0
18
29
0
0
rh0gue's profile picture. @OpenToAllCTF and @SamuraiCTF
Josh Wang
 @rh0gue
2018. 1. 9.

Thank you for writing this challenge and for putting together #34c3ctf. I learned a lot!

0
0
2
0
0
bkth_'s profile picture. Building a conglomerate @dfsec_com
Bruno
 @bkth_
2018. 1. 8.

Pretty neat write-up for a simple pwnable challenge I did for #34c3ctf, if you are interested in learning more about some of the latest glibc allocator developments: blog.rh0gue.com/2018-01-05-34c…

3
21
57
0
0
_niklasb's profile picture. research @dfsec_com - @niklasb@infosec.exchange
Niklas B
 @_niklasb
2018. 1. 7.

Wargames and CTFs that are doable for beginners like PicoCTF, SHA CTF Junior and #34c3ctf Junior.

1
0
6
0
0
eboda_'s profile picture.
eboda
 @eboda_
2018. 1. 5.

I made a quick writeup for my extract0r web challenge from the #34c3ctf github.com/eboda/34c3ctf/…

0
8
18
0
0
Yannayli's profile picture. Warranty voider | Occasional exploiter | Holistic Security researcher | Views are deconstructed | The author will die (E&OE)
Yannayl
 @Yannayli
2018. 1. 3.

My writeup on #34c3ctf 300 challenge: github.com/chksum0/writeu… tldr: House of Orange + vtable validation bypass

1
6
15
0
0
lmscientist's profile picture. I am the Lazy Mad Scientist!
Lazy Mad Scientist
 @lmscientist
2018. 1. 3.

Maybe should make a #findmyunicorn and see how many replies it gets? #34C3 #34c3ctf

0
0
0
0
0
_tsuro's profile picture. @v8js security, CTFs and CPU vulnz. LCHL. @tsuro@infosec.exchange
stephen
 @_tsuro
2018. 1. 2.

Here's my exploit for my heap challenge (300) of the #34c3ctf. I solved it by overwriting (older) libc's check_action variable using a corrupted unsorted bin. This disables abort on error and gives a write-what-where primitive. gist.github.com/sroettger/591b…

_tsuro's tweet card. One solution for the 34c3ctf's 300 heap challenge. - 300.py
One solution for the 34c3ctf's 300 heap challenge.
출처: gist.github.com
1
8
42
0
0
"#34c3ctf"에 대한 결과가 없습니다
"#34c3ctf"에 대한 결과가 없습니다

Something went wrong.


Something went wrong.


United States Trends