Anthony J. Fontanez

123 Followers
134 Following
22 Posts
• Lead Customer Engineer (Intune/ConfigMgr)
• IT Professional in the Microsoft space (#ConfigMgr, #Intune, #ActiveDirectory, #AzureAD)
• Endpoint Management enthusiast and blogger
• Admin for the #WinAdmins Discord Community
• Part-time gamer when my brain is fried from other stuff
About Mehttps://ajf.one/me
Bloghttps://anthonyfontanez.com
Blueskyhttps://bsky.app/profile/ajf8729.com
GitHubhttps://github.com/ajf8729
WinAdmins Communityhttps://winadmins.io

So this "CVSS 9.9" "unauthenticated RCE vs all GNU/Linux systems (plus others)" thing...

- Does NOT affect all GNU/Linux systems.
- Is not CVSS 9.9. I put it at a 6.3

It also requires:
1) The victim system has no active firewall to block incoming connections.
2) A user on the victim system must print something to a printer that mysteriously appears on the system that has never been there before.

If these two things happen, then command execution can happen as the "lp" user.

<yawn>

We get it. You found a vulnerability.
Lying about it to try to stir up interest in it is not appreciated by anybody who takes themselves seriously in this industry.

CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177 have been assigned.

https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/

Attacking UNIX Systems via CUPS, Part I

Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start with targeting GNU/Linux systems with an RCE. As someone who’s

evilsocket
@Tarah Neither, use native Entra ID and WHfB or FIDO keys for MFA. ADFS not required. On-premises anything not required.
CVE-2023-32019 (KB5028407) requires an additional registry value be configured to enable the fix; I put together some scripts that can be used via #ConfigMgr DCM to detect/remediate, as well as handle the different OS builds and registry paths/settings. I also recently updated this to include similar scripts that can be used via #Intune [Proactive] Remediation - https://ajf8729.com/post/cve-2023-32019-kb5028407-registry-settings/
Managing the Registry Settings for CVE-2023-32019 (KB5028407)

How to configure the necessary registry settings for CVE-2023-32019 - KB5028407 via PowerShell, ConfigMgr DCM, and Intune

AJF8729
How to quickly and easily modify #ConfigMgr Client Settings profiles via #PowerShell, an issue I recently ran into: https://ajf8729.com/post/modifying-client-settings-priorities/
Modifying Client Settings Priorities With PowerShell

How to easily modify ConfigMgr Client Settings priorities with PowerShell

AJF8729
Desktop Analytics is being retired in a week! I just went through removing it from my lab, and found one reference to the AAD application left behind that needed to be removed via WMI: https://ajf8729.com/post/removing-desktop-analytics/ #ConfigMgr
Removing Desktop Analytics from your ConfigMgr Site

How to remove Desktop Analytics and clean up everything left behind

AJF8729
Another #ConfigMgr Quick Post today - How to quickly set all of your Configuration Baselines to run on co-managed devices via #PowerShell - https://ajf8729.com/post/enabling-baselines-for-comanaged-devices/
Enabling Configuration Baselines for Co-managed Clients

Problem: You’ve shifted the “Device Configuration” workload in your ConfigMgr site to Intune, and your existing Configuration Baselines are no longer applying, and there’s a lot of them. Solution: Spend the next two hours clicking away in the console PowerShell of course! 1 Get-CMBaseline -Fast | Set-CMBaseline -AllowComanagedClients $true Running the above one-liner will enable all of your existing baselines to be run on co-managed clients even when the workload has been shifted to Intune.

AJF8729

I love all of you and I want nothing but the best for each of you, particularly those on infosec.exchange. I understand that Mastodon isn't Twitter, that DMs aren’t end-to-end encrypted, that we are spread across different instances and it can be hard to find your friends, and that an instance can go away at any time, and that translating posts doesn't work correctly, and there is no native giphy support, and that some instances are overwhelmed and super slow, and that you don't think the federated model can scale to a billion users, or that it doesn't support full text search of every post and account, or that we can't comply with the GDPR, or that we don't support quote tweet style functionality, or that we shouldn't collect IP addresses, and many other things.

The fediverse is a work in progress. I've been here for going on 6 years. In that time, it's come a long, long way. That said, Mastodon is not going to appeal to everyone. The decisions I make are not going to appeal to everyone. No one is forcing you to be here. No one is forcing you to disclose your personal secrets into a network of federated servers running by volunteers and hobbyists. NB: this is not Twitter. It has some similar functionality, but it is not Twitter. Parts of it are better, IMO, and parts are not. The security community is generally among the most skilled and competent IT people the world has to offer. Mastodon is open source. Do you see where I'm going?

I set this instance up a long time ago for reasons I don't even remember. I have poured my soul into this thing because I believe in the importance of this community. I have effectively peaked in my career as a CISO and I and my family live well. I am not running this instance for fame, money, a better job, or anything other than wanting to foster a community of people that can learn from each other and make the world a better place. That's it.

As I've said in several recent interviews, I felt particularly obligated to ensure the security community had a good landing spot in the fediverse as everyone was running for the doors in Twitter. We've grown from 180 active users to about 30000 in the span of 3 weeks. I do not expect everyone to stay. Some will set up their own instances. Some will move to one of the other excellent security focused instances. Some will give up and move to on to some other social media. And that is OK. While I am super excited to see the buzz here, I don't have subscriber targets, engagement targets, retention targets, or anything else. The only metric I hold myself to is whether I think this is serving a useful purpose to the community.

I appreciate all of you, regardless of where you land. Infosec.exchange has been here for a long time and will continue to be here for you.

Find your #configmgr peeps. #findme_memcm
ping in the dark 🔦
#findme_memcm
Someone suggested this experiment… #findme_memcm