summaryrefslogtreecommitdiff
path: root/posts/Bad BEHAVIOR/bad-behavior.org
diff options
context:
space:
mode:
authorJakob L. Kreuze <zerodaysfordays@sdf.lonestar.org>2019-05-11 08:29:44 -0400
committerJakob L. Kreuze <zerodaysfordays@sdf.lonestar.org>2019-05-11 08:29:44 -0400
commit8d4f38027b3baeead5da2399431649241ebab73e (patch)
tree9a96afae00bbccda5786ccf2933820742c5f2f12 /posts/Bad BEHAVIOR/bad-behavior.org
parent43a0084358370d0e735fe98b567250d03d983f2a (diff)
Import publication times
Diffstat (limited to 'posts/Bad BEHAVIOR/bad-behavior.org')
-rw-r--r--posts/Bad BEHAVIOR/bad-behavior.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/posts/Bad BEHAVIOR/bad-behavior.org b/posts/Bad BEHAVIOR/bad-behavior.org
index e559692..87e0ae7 100644
--- a/posts/Bad BEHAVIOR/bad-behavior.org
+++ b/posts/Bad BEHAVIOR/bad-behavior.org
@@ -1,5 +1,5 @@
#+TITLE: Bad BEHAVIOR
-#+DATE: <2018-01-04 Thu>
+#+DATE: <2018-01-04 Thu 15:45>
#+TAGS: writeup, security, binary-exploitation, video-games, x86, doom
TL;DR, I discovered a stack-smashing vulnerability in GZDoom's interpreter for