If it's so easy to guess a uuid, here you go
I ran crypto.randomUUID() twice on my machine.
The first ID was 15041508-fd38-4eda-bc1d-7b74e4738cd9
The second? That's your challenge.
I encrypted a text file with the following command:
If it's so easy to guess a uuid, here you go
I ran crypto.randomUUID() twice on my machine.
The first ID was 15041508-fd38-4eda-bc1d-7b74e4738cd9
The second? That's your challenge.
I encrypted a text file with the following command:
| from z3 import * | |
| xs = [BitVec('x{}'.format(i), 8) for i in xrange(25)] | |
| s = Solver() | |
| for x in xs: | |
| s.add((x & ~0xff) == 0) | |
| s.add(xs[0] == 101) | |
| s.add(xs[14] ^ xs[0] == 14) |
| // ==UserScript== | |
| // @name mbank unlifting | |
| // @description Przywraca wygląd strony transakcyjnej mbanku z przed liftingu | |
| // @version 0.1 | |
| // @grant none | |
| // @author mardr | |
| // @include https://online.mbank.pl/* | |
| // ==/UserScript== | |
| document.documentElement.classList.remove('lifting'); |
| /* Plaid CTF 2018 v8 Exploit. Exploit begins around line 240 */ | |
| /* ### Utils, thanks saelo ### */ | |
| // | |
| // Tiny module that provides big (64bit) integers. | |
| // | |
| // Copyright (c) 2016 Samuel Groß | |
| // |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <stdint.h> | |
| #ifdef _MSC_VER | |
| #include <intrin.h> /* for rdtscp and clflush */ | |
| #pragma optimize("gt",on) | |
| #else | |
| #include <x86intrin.h> /* for rdtscp and clflush */ | |
| #endif |
| #include <cstdio> | |
| #include <ctime> | |
| #include <iostream> | |
| using namespace std; | |
| const __int32 start_time = 1500465600; // guessed time | |
| const __int32 end_time = 1500498000; // guessed time | |
| __int8 encryptedMessage[] = |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
Although there are many excellent resources for learning Volatility available (The Art of Memory Forensics book, the vol-users mailing list, the Volatility Labs blog, and the Memory Analysis training course to name a few), I've never really seen a good absolute beginners guide to writing your first plugin. So if you find yourself needing that, hopefully this will help.
Also, it's worth checking out @jameshabben's post on the topic.
| MIT License | |
| Copyright (c) 2018 Jason Sperske | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights | |
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: |