-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does linpeas still detect CVE-2021-3560? #339
Comments
I just saw it falsely detect it on another box (investigation). |
If you run this command,
Then Polkit does not even appear to show up as an installed package if I understand this correctly (it's a CentOS server). Welcome any correction to my understanding; thanks! the suggestion in #332 does appear to work though (at least the raw command appears to meet the condition. |
Ah, sorry for the duplicate. These issues should probably be merged. The walkthrough of paper says that it should detect it, so something must've changed. Diving into the commits changing that code might give some clarity. Might do that later. |
hi guys! did you figure this out? |
My only guess is that the changes in 999fcff broke the detection. I will investigate further. |
So there's two issues with that commit that breaks detection on the paper box. The first issue is the polkit package is searched with
In this box the package was most likely manually installed with The new query also only searches for version It used to also check I am also not sure why it would search for those exact pkgrel versions. I also think searching for packages via There's currently also an entirely unused variable |
I can confirm that this is still a problem |
Hi guys! |
I was doing the HackTheBox box "Paper", which uses the polkit CVE-2021-3560 for privilege escalation.
In the walkthrough for this box, linpeas suggests the CVE in the
CVEs Check
section with a red on yellow background. But on the latest release of linpeas the CVE is not even suggested.The text was updated successfully, but these errors were encountered: