-
Notifications
You must be signed in to change notification settings - Fork 187
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
Actively Exploited CVEs displays "false" when using -simulate-os-version flag #610
Comments
You're misunderstanding how this logic works. While you are correct that 14.3.1 has active exploits, this bug report is not valid. If you are wanting a feature request to loop through ALL updates from x version through y version for active exploits, then show that as This issue gives the impression this behavior is wrong, and it is not. You are simulating a macOS version to test the that your core nudge config is correct. |
My apologies. This was indeed meant to be a feature request and not a bug report. Thank you for clarifying. |
It's an interesting feature request and one that will likely take a new thought around the sofa code. I'm willing to entertain it so please submit a feature request issue for this so I don't forget. |
Gentle ping to not forget :) |
I made a ticket myself. |
Hey! Sorry for the delay on this, and thank you so much! |
While testing with the
-simulate-os-version
flag (thank you for this btw!), it seems Nudge will display False when passing a version of macOS that is known to have actively-exploited CVEs.For example, running
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -simulate-os-version "14.3.1"
displays this info:Nudge recommends macOS 14.5 as expected, but it does not appear to acknowledge that 14.3.1 has two actively-exploited CVEs that were addressed in 14.4.
I'm assuming Nudge is only reading the CVE details for macOS 14.5 but it would be a nice enhancement for it to consider any updates that were issued between the latest version and what is currently installed on the device.
The text was updated successfully, but these errors were encountered: