okla.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Oklahoma... we're trying ya'll

Administered by:

Server stats:

33
active users

#pentest

9 posts8 participants1 post today
r1cksec<p>RunAs Utility Credential Stealer implementing 3 techniques : Hooking CreateProcessWithLogonW, Smart Keylogging, Remote Debugging 🕵️‍♂️ </p><p><a href="https://github.com/DarkSpaceSecurity/RunAs-Stealer" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/DarkSpaceSecurity/R</span><span class="invisible">unAs-Stealer</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/redteam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redteam</span></a></p>
0x40k<p>Whoa, this is seriously messed up! Just finished reading an article about the compromised GitHub Action `tj-actions/changed-files`. Get this – over 23k repos were affected! That's a huge deal, right? 😳</p><p>Turns out, CI/CD Secrets (think AWS Keys, Tokens, the whole shebang) were snatched. It's CVE-2025-30066 – a full-blown Supply Chain Attack! 💣</p><p>So, what happened? Well, the attacker modified the code and tampered with the version tags. Then, the Action diligently packed Secrets into Build-Logs… ouch! 😬</p><p>And why is this so bad? Supply Chain, folks! Open Source is fantastic, no doubt, but keeping things in check is absolutely crucial! It kinda reminds me of a Pentest we did where we nearly missed something... 😅</p><p>Alright, here's what you gotta do: Update to 46.0.1 *immediately*! Plus, take a look at your workflows from the 14th-15th. I just had this issue pop up with a client... Update done, problem solved! 💪 Also, remember the Least Privilege Principle! Keep a close eye on Open Source stuff, always!</p><p>Open-Source Security is still incredibly important! You've got to take Supply Chain risks seriously! Because, security is a continuous process, not a product you just buy! It's like those customers who think ISO 27001 solves all their problems... 🙄</p><p>So, have you guys experienced similar horror stories? What tools do you use for Supply Chain Security? What are your biggest Open-Source nightmares? Share them below! 👇</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/supplychainattack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>supplychainattack</span></a></p>
r1cksec<p>A simple C++ Windows tool to get information about processes exposing named pipes🕵️‍♂️ </p><p><a href="https://github.com/p0dalirius/FindProcessesWithNamedPipes" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/p0dalirius/FindProc</span><span class="invisible">essesWithNamedPipes</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/redteam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redteam</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a></p>
0x40k<p>Hey everyone, does this sound familiar? You install a Python package and suddenly feel like you've been robbed blind? 😂</p><p>Right now, there's a nasty campaign going on targeting PyPI, and it's misusing "time" utilities to swipe cloud credentials. Get this – it's already had over 14,000 downloads! The malware hides in packages that are *supposed* to just check the time. But instead, they're snatching cloud keys (AWS, Azure, the works) and sending them straight to the bad guys.</p><p>Honestly, it reminds me of a pentest we did where we *almost* missed a similar camouflage trick. Seriously creepy! So, heads up: Double-check your dependencies, run those scans, review your cloud configurations, and above all, be suspicious! And hey, just a friendly reminder: automated scans are no substitute for a manual pentest!</p><p>Have you run into anything similar? What tools are you using to beef up your security? Let's chat about it!</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a> <a href="https://infosec.exchange/tags/pypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pypi</span></a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/cloudsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cloudsecurity</span></a></p>
0x40k<p>Alright everyone, let's talk microsegmentation – seriously crucial, but it's easy to overlook! 🙄 A lot of folks assume a firewall's enough, but what happens when an attacker's *already* inside your network? That's where microsegmentation comes to the rescue. Think of it as having a second, third, or even fourth firewall *within* your network. 💪</p><p>Our clients *always* appreciate it when we demonstrate the need for this through penetration tests. Of course, it's often a question of budget, but honestly, security shouldn't be compromised! ☝️</p><p>So, how are *you* segmenting your networks? Got any experiences, preferred tools, or insights to share? Let's hear 'em! Go!</p><p><a href="https://infosec.exchange/tags/ITSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ITSecurity</span></a> <a href="https://infosec.exchange/tags/Pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pentest</span></a> <a href="https://infosec.exchange/tags/ZeroTrust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ZeroTrust</span></a></p>
0x40k<p>Ransomware totally sucks, right? 😡 But ignoring it? That's just not gonna cut it. Just finished watching a webinar, "From Breach to Ransom" – basically, it walks you through how they go from finding a hole in your system to demanding a payout.</p><p>And why is this stuff important, you ask? Well, it really shines a light on how attackers *actually* operate. Think exploits, lateral movement within your network... As a pentester, I'm constantly seeing companies get tripped up by outdated software. Honestly, some of it's just mind-blowing! 🤦‍♂️ And let's be real, automated vulnerability scans? Those aren't the same as a proper pentest. Not even close.</p><p>So, what are your biggest ransomware worries? I'm curious, share your experiences in the comments below! 👇</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
0x40k<p>Seriously, backups... still such a headache, right? 🤯 Just stumbled across some stats that suggest a ton of companies are WAY overconfident about their recovery readiness. Seriously, WTF?!</p><p>Yeah, the cloud's great and all, but let's be real – if you don't have a Plan B (and C, D...), you're toast. Sorry, not sorry, for being blunt. 🙈</p><p>As a pentester, I see this all the time: Backups are there, sure, BUT... they've never actually been tested. Or they're secured with super old, outdated credentials. Hello, ransomware! 👹</p><p>Here's my two cents: Backups HAVE to be an integral part of your security strategy, not just some afterthought. We're talking regular testing, preferably automated. And those cloud backups? You've gotta double-check those access permissions! Shadow IT is a HUGE risk! ⚠️</p><p>What do you guys think? Are backups just a pain in the butt compliance thing, or are they more like a vital insurance policy? 🤔</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backup</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/cloudsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cloudsecurity</span></a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ransomware</span></a></p>
Mänu<p>The second part is about bypassing web filters via Host header spoofing: <a href="https://blog.compass-security.com/2025/03/bypassing-web-filters-part-2-host-header-spoofing/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.compass-security.com/2025</span><span class="invisible">/03/bypassing-web-filters-part-2-host-header-spoofing/</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>network</span></a></p>
0x40k<p>Alright folks, gotta share something kinda alarming I just read: SSRF attacks are seriously picking up steam! 🤯 For those who don't know, SSRF (Server Side Request Forgery) is nasty business. Basically, attackers can trick your server into making requests *for* them. Think internal network snooping, stealing cloud credentials... you know the drill.</p><p>And get this – it's hitting tons of systems at once (DotNetNuke, Zimbra, VMware, GitLab, Ivanti, you name it!). It almost feels like a coordinated attack, doesn't it?</p><p>It's especially dicey in the cloud because SSRF can be used to access internal metadata APIs. Yikes!</p><p>I'm telling you, I once did a pentest where we almost completely missed an SSRF vulnerability being used to compromise internal AWS resources. It was a super close call! 😅</p><p>So, here's what you should do, pronto:</p><p>* **Patch like your life depends on it!** (Seriously, this isn't optional)<br>* **Restrict outgoing connections** (Least Privilege is your best friend here!)<br>* **Monitor those outgoing requests** (Gotta catch any suspicious behavior)<br>* **Network segmentation** (This can seriously limit the damage)</p><p>AI can be helpful for spotting anomalies, but remember: AI is NOT a pentest! Automated scans are nice, but they're no replacement for actual human expertise.</p><p>Are you seeing more SSRF attacks lately? What tools are you using to detect them? Let me know in the comments.</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/ssrf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ssrf</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/cloudsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cloudsecurity</span></a></p>
Mänu<p>I wrote a blog post series about bypassing web filters / proxies. Part one is about SNI spoofing. You can read it here: <a href="https://blog.compass-security.com/2025/03/bypassing-web-filters-part-1-sni-spoofing/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.compass-security.com/2025</span><span class="invisible">/03/bypassing-web-filters-part-1-sni-spoofing/</span></a></p><p><a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>network</span></a></p>
0x40k<p>Steganography's seriously sneaky! Hiding malware *inside* seemingly innocent pictures? Yep, that's a thing. And guess what? Most antivirus software and similar tools? They completely miss it. I just read about how XWorm's doing it: they're using PDF phishing to distribute a REG file, which then triggers PowerShell to pull a DLL payload from an image. BOOM! Data theft's about to happen.</p><p>You know, clients I've helped have been so grateful when we've uncovered stuff like this. It's a constant process, though. Always gotta be on the lookout!</p><p>So, what do *you* think? Are automated scans enough to catch this stuff, or do we need more human expertise to really stay secure? Let me know what you think!<br><a href="https://infosec.exchange/tags/ITSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ITSec</span></a> <a href="https://infosec.exchange/tags/Pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pentest</span></a> <a href="https://infosec.exchange/tags/Malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Malware</span></a></p>
0ddj0bb<p>Hey <a href="https://infosec.exchange/tags/redteam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redteam</span></a> and <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> ers, what security controlsnon endpoints and servers make your life miserable on an engagement? </p><p>App allow listing? <br>DEP?<br>Powershell execution policies?<br>Hostbased firewall?</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/hacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hacking</span></a> <a href="https://infosec.exchange/tags/cyber" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cyber</span></a> <a href="https://infosec.exchange/tags/dfir" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dfir</span></a></p>
r1cksec<p>A Windows standalone executable tool that allows you to change the password of user/computer accounts in Active Directory (AD) via MS-SAMR protocol🕵️‍♂️ </p><p><a href="https://github.com/decoder-it/ChgPass" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/decoder-it/ChgPass</span><span class="invisible"></span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/redteam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redteam</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a></p>
0x40k<p>Chrome Extensions: Masters of Disguise at Work! 🎭</p><p>Heads up, folks! There's a seriously nasty new wave of attacks going around: fake Chrome extensions are out there, and they're stealing your data! 😱 These things are so good at mimicking the icons and pop-ups of your favorite add-ons, you might not even realize what's happening. And it affects Chrome, Edge, basically everything!</p><p>Here's the really sneaky part: the extension doesn't *immediately* do anything bad. Instead, it quietly figures out which add-ons you're using. Then, BAM! It transforms itself, temporarily disabling the real extension. Next thing you know – login credentials stolen, account gone! 💸</p><p>Speaking as a pentester, I've gotta say, this is some impressive social engineering. Automated scans won't catch this stuff because, hey, the extension appears to be "working" just fine. So, a bit of human intelligence and healthy skepticism are absolutely essential here.</p><p>My advice? Always take a *very* close look at new extensions before you install them. Double-check the permissions they're asking for! Does it *really* need access to *everything*? And remember, regular pentests are worth their weight in gold.</p><p>So, have you had any experiences with these fake extensions? How do *you* protect yourself? What tools do you use to spot suspicious Chrome extensions? Let's share some tips in the comments!<br><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/chrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chrome</span></a></p>
0x40k<p>Alright folks, let's talk AI. It's cool and all, but a lot of people are overlooking something crucial: Security *has* to be baked in from the start! Seriously, you can't just add it later when things go south.</p><p>I just had a client who was all, "Oh, we'll worry about security down the road." Well, guess what? Data breach and a *massive* fine. Devs need to be embracing security, not just ticking it off a list. Oh, and automated scans? They are *not* a substitute for a real pentest!</p><p>So, what do you think is the biggest hurdle when it comes to weaving security into the development process? I'm curious to hear your thoughts.</p><p><a href="https://infosec.exchange/tags/DevSecOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevSecOps</span></a> <a href="https://infosec.exchange/tags/SecurityFirst" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecurityFirst</span></a> <a href="https://infosec.exchange/tags/Pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pentest</span></a></p>
0x40k<p>Whoa, this week was a total rollercoaster in cybersecurity! 🤯 Seriously, state-sponsored hackers, ransomware attacks, and phishing attempts were all over the place. Things are definitely escalating quickly! 💣</p><p>Sure, a firewall is important – no doubt about it. But honestly, it's just not enough these days. We've gotta build awareness, learn to spot patterns, and connect the dots. 🧩 Otherwise, vendors will just keep pushing solutions we don't even need. 🙄 It is important to start thinking more critical about that.</p><p>You know, binary whitelisting is a relatively easy win when dealing with "Living off the Land" attacks! 💪 And by the way, Open Source totally rocks! 🤘</p><p>So, what are your biggest cybersecurity worries right now? 🤔 Let's chat about it! What keeps you up at night?</p><p>\<a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> \<a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> \<a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
r1cksec<p>An article about the security implications of abandoned third-party JavaScript libraries🕵️‍♂️ </p><p><a href="https://blog.fraktal.fi/examining-external-dependencies-in-web-applications-0846894cecdd" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.fraktal.fi/examining-exte</span><span class="invisible">rnal-dependencies-in-web-applications-0846894cecdd</span></a></p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a> <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>javascript</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/redteam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>redteam</span></a></p>
0x40k<p>Ragnar Loader... another one of those things you see and initially think, "Okay, nothing special." But then you realize just how wild this thing really is. 😅</p><p>Loaders aren't exactly groundbreaking, but Ragnar Loader seriously takes it to the next level. Various ransomware gangs are using it almost like a "Malware-as-a-Service" platform. And get this – they're constantly developing and improving it. 🤯</p><p>Reverse shell capabilities, privilege escalation, stealth... it's got the works. As a pentester, sadly, you see this kinda stuff all the time. It just highlights how crucial security awareness and routine checks really are. Updates are non-negotiable! And yeah, I know, "Updates are annoying," but hey, I think paying a ransom is even more annoying. 🤷‍♂️</p><p>What's your take on this? Are automated vulnerability scans enough, or do we need to step it up? <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a> <a href="https://infosec.exchange/tags/ragnarloader" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ragnarloader</span></a></p>
0x40k<p>Whoa, check this out! 🤯 A million devices infected via malvertising! Seriously scary stuff. You know, those illegal streaming sites? Total playground for cybercriminals.</p><p>Malvertising is a real nasty piece of work, isn't it? They sneak malware in through ads. Gotta remember: even "free" stuff comes with a cost, right?</p><p>This Lumma Stealer thing grabs your passwords, and these RATs (Remote Access Trojans) let them control your system remotely. And get this – they're abusing GitHub to host the malware. Ugh. 😒</p><p>It actually reminds me of a pentest we did where we almost missed an attack chain just like this. You really gotta stay vigilant! ☝️</p><p>So, what does it mean for you? Well, a firewall's great, but it's not a magic bullet. Double-check your downloads, and be super skeptical of any links.</p><p>Microsoft's calling these guys "Storm-0408." Apparently, they're using PowerShell, messing with Defender, and even faking AI chatbot sites! 🤖 Sneaky!</p><p>Bottom line: steer clear of those shady streaming sites. Be wary of links! Keep your antivirus updated. Keep an eye on PowerShell. And most importantly: run regular pentests! 🔒</p><p>Ever had a run-in with malvertising? How do *you* stay safe? 🤔 Share your tips!</p><p><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentest</span></a></p>
usd AG<p>If you're using the <a href="https://infosec.exchange/tags/Cubro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cubro</span></a> EXA48200 network packet broker, you should update to V5.0R14.5P4-V3.3R1.</p><p>Our expert, Tim Wörner, discovered a broken access control vulnerability in the user management API, which leads to privilege escalation (CVE-2024-55570).</p><p>📌 Read the full details here: <a href="https://herolab.usd.de/en/security-advisories/usd-2024-0014/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">herolab.usd.de/en/security-adv</span><span class="invisible">isories/usd-2024-0014/</span></a></p><p><a href="https://infosec.exchange/tags/CVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CVE</span></a> <a href="https://infosec.exchange/tags/AppSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AppSec</span></a> <a href="https://infosec.exchange/tags/Cubro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cubro</span></a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InfoSec</span></a> <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/Hacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hacking</span></a> <a href="https://infosec.exchange/tags/Pentest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pentest</span></a> <a href="https://infosec.exchange/tags/CVE_2024_55570" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CVE_2024_55570</span></a></p>