CollabVM Wikia/Socket.io: Difference between revisions
import>Dartz m 7 revisions imported: CollabVM Wikia Articles |
m 14 revisions imported |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{CollabVM Wikia}}<br/> | |||
Originally, CollabVM was run on (shitty) software called Socket.io. Full of vulnerabilities, this was the basis of Dartz' growing site. One infamous guy, Debianguy(Colonial Seizureton or the guest that keeps installing Tiny Core Linux) abused exploits to send a shutdown command directly to qemu command lines. Those same vulnerabilities exist on socket.computer, despite the owner aware of their possible effects on the server. Those vulnerabilities are not to be disclosed, because, if used correctly(or incorrectly) one could overwrite node.js modules that are critical to servers all over the world. Dartz has since sent ways to fix these vulnerabilities, but the lazy-ass dev refuses to put them in use. So here he stands, waiting for someone to pmemsave the whole fucking server | Originally, CollabVM was run on (shitty) software called Socket.io. Full of vulnerabilities, this was the basis of Dartz' growing site. One infamous guy, Debianguy(Colonial Seizureton or the guest that keeps installing Tiny Core Linux) abused exploits to send a shutdown command directly to qemu command lines. Those same vulnerabilities exist on socket.computer, despite the owner aware of their possible effects on the server. Those vulnerabilities are not to be disclosed, because, if used correctly(or incorrectly) one could overwrite node.js modules that are critical to servers all over the world. Dartz has since sent ways to fix these vulnerabilities, but the lazy-ass dev refuses to put them in use. So here he stands, waiting for someone to pmemsave the whole fucking server | ||
The countdown begins. How long before someone overwrites his socket.computer snapshot with a command to delete the System32 folder at startup or have the hard drive only with junk and no OS? Give it about a few months and it's bound to happen. | The countdown begins. How long before someone overwrites his socket.computer snapshot with a command to delete the System32 folder at startup or have the hard drive only with junk and no OS? Give it about a few months and it's bound to happen. | ||
Latest revision as of 23:56, 19 December 2024
Template:CollabVM Wikia
Originally, CollabVM was run on (shitty) software called Socket.io. Full of vulnerabilities, this was the basis of Dartz' growing site. One infamous guy, Debianguy(Colonial Seizureton or the guest that keeps installing Tiny Core Linux) abused exploits to send a shutdown command directly to qemu command lines. Those same vulnerabilities exist on socket.computer, despite the owner aware of their possible effects on the server. Those vulnerabilities are not to be disclosed, because, if used correctly(or incorrectly) one could overwrite node.js modules that are critical to servers all over the world. Dartz has since sent ways to fix these vulnerabilities, but the lazy-ass dev refuses to put them in use. So here he stands, waiting for someone to pmemsave the whole fucking server
The countdown begins. How long before someone overwrites his socket.computer snapshot with a command to delete the System32 folder at startup or have the hard drive only with junk and no OS? Give it about a few months and it's bound to happen.