pocorgtfo
gitlab-workhorse
pocorgtfo | gitlab-workhorse | |
---|---|---|
7 | 2 | |
1,223 | - | |
- | - | |
5.8 | - | |
3 months ago | - | |
TeX | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pocorgtfo
-
MIPS Firmware Reverse Engineering - anyone having any success using Ghidra for this?
Your best bet here is to get the base address nailed down (assuming it’s a flat/monolithic image). There are a handful of utilities floating around (binbloom, basefind2) that use various pointer heuristics to try to guess the base address. There’s also a nice trick detailed in PoC||GTFO that you can use pretty reliably.
- Image displays its own MD5 hash
- Gitlab servers are being exploited in DDoS attacks in excess of 1 Tbps
-
smh dumb antivirus software
execute the pdf: https://github.com/angea/pocorgtfo
-
SHA-1 'Fully and Practically Broken' by New Collision
1) People systematically underestimate how easy it is to create collisions that still do something "interesting", like being polyglots. See PoC||GTFO, specifically anything by Ange Albertini, for examples; grep https://github.com/angea/pocorgtfo/blob/master/README.md for "MD5".
1bis) You can use an existing collision to create new collisions. People seem to think you need to generate all the work again from scratch.
1cis) The files do not need to be gigantic.
2) You can do the collision in advance, and publish the malicious version later. What it accomplishes is that the concept of "this Git hash unambiguously specifies a revision" no longer works, and one of them can be malicious.
3) The standard should be "obviously safe beyond a reasonable doubt", not "not obviously unsafe to a non-expert". By the latter standard, pretty much any random encryption construction is fine.
-
Show HN: Redbean: single-file distributable web server
If you want to learn more how these things work I'd highly suggest going through the PoC||GTFO archive (https://github.com/angea/pocorgtfo/blob/master/README.md) and check out entries by Ange Albertini or entries named like "This ZIP is also a PDF".
gitlab-workhorse
-
Gitlab servers are being exploited in DDoS attacks in excess of 1 Tbps
The first step is always "don't do it at all". Here is the original commit:
https://gitlab.com/gitlab-org/gitlab-workhorse/-/commit/8656...
It's hard to find a linked detailed requirement for this. I would certainly prefer if GitLab didn't mangle uploaded images (not least if I'm working on an EXIF library..).
-
Installing gitlab with docker: it shows me only a 502 page
I found this https://gitlab.com/gitlab-org/gitlab-workhorse/-/issues/129 and
What are some alternatives?
polyshell - A Bash/Batch/PowerShell polyglot!
Judge0 API - 🔥 The most advanced open-source online code execution system in the world.
exiftool - ExifTool meta information reader/writer
gitlab
RedBean - ORM layer that creates models, config and database on the fly
Metasploit - Metasploit Framework
sha1collisiondetection - Library and command line tool to detect SHA-1 collision in a file
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
CVE-2021-4034 - CVE-2021-4034: Local Privilege Escalation in polkit's pkexec proof of concept