Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The exploit code for CVE-2022-2585 shared by SSD Secure Disclosure was corrupted (on their original page at https://ssd-disclosure.com/ssd-advisory-linux-clock_thread_cputime_id-lpe/):
\nnewline characters in C strings had been converted to the lettern. This broke at least one key function, and also caused console output to be formatted poorly.#(e.g.# define), that first pound sign was stripped, which prevented compilation because it broke two#definestatements.The version in this repo was also missing the customized
libexp.cincluded in the SSD Secure Disclosure post. That file is necessary because it contains quite a few functions referred to inexploit.c.Finally, I added instructions for compiling the exploit, because it's not just
makeorgcc -o exploit exploit.cin this case.