Aggregator
CVE-2025-31359 | Parallels Desktop 20.2.2 (55879) on macOS PVMP Package Unpacking path traversal (TALOS-2025-2160 / EUVD-2025-16718)
CVE-2024-54189 | Parallels Desktop 20.1.1 on macOS Snapshot unix hard link (TALOS-2024-2124 / EUVD-2024-54642)
CVE-2024-52561 | Parallels Desktop 20.1.1 on macOS Snapshot incorrect ownership assignment (TALOS-2024-2123 / EUVD-2024-54641)
CVE-2024-36486 | Parallels Desktop 20.1.1 on macOS Virtual Machine Archive Restoration prl_vmarchiver unix hard link (TALOS-2024-2126 / EUVD-2024-54643)
Honoring Innovation, Growth, and Collaboration: The Akamai Partner Awards
CISA Adds Three Known Exploited Vulnerabilities to Catalog
CISA has added three new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation.
- CVE-2025-21479 Qualcomm Multiple Chipsets Incorrect Authorization Vulnerability
- CVE-2025-21480 Qualcomm Multiple Chipsets Incorrect Authorization Vulnerability
- CVE-2025-27038 Qualcomm Multiple Chipsets Use-After-Free Vulnerability
These types of vulnerabilities are frequent attack vectors for malicious cyber actors and pose significant risks to the federal enterprise.
Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities established the KEV Catalog as a living list of known Common Vulnerabilities and Exposures (CVEs) that carry significant risk to the federal enterprise. BOD 22-01 requires Federal Civilian Executive Branch (FCEB) agencies to remediate identified vulnerabilities by the due date to protect FCEB networks against active threats. See the BOD 22-01 Fact Sheet for more information.
Although BOD 22-01 only applies to FCEB agencies, CISA strongly urges all organizations to reduce their exposure to cyberattacks by prioritizing timely remediation of KEV Catalog vulnerabilities as part of their vulnerability management practice. CISA will continue to add vulnerabilities to the catalog that meet the specified criteria.
CISA Releases Three Industrial Control Systems Advisories
CISA released three Industrial Control Systems (ICS) advisories on June 3, 2025. These advisories provide timely information about current security issues, vulnerabilities, and exploits surrounding ICS.
- ICSA-25-153-01 Schneider Electric Wiser Home Automation
- ICSA-25-153-02 Schneider Electric EcoStruxure Power Build Rapsody
- ICSA-25-153-03 Mitsubishi Electric MELSEC iQ-F Series
CISA encourages users and administrators to review newly released ICS advisories for technical details and mitigations.
New NIST Standard Helps Deliver the Right Dosage of Cancer-Fighting Drugs
Posture ≠ Protection
CSPM, DSPM, ASPM, SSPM, ESPM — the alphabet soup of Security Posture Management (SPM) tools promises visibility into risk. They map misconfigurations, surface exposure paths and highlight policy gaps. That can be useful. But let’s not confuse awareness with action.
They don’t block threats.They don’t enforce controls.
They don’t prevent breaches.
SPMs detect, then delegate. A ticket. A Slack alert. An integration call. Protection is someone else’s problem.
To compensate, many posture tools claim to orchestrate security. They integrate with enforcement tools like DLP, CWPP, EDR and WAF. But wiring systems together doesn’t make the system secure.
Coordination ≠ ProtectionVisibility ≠ Control
Monitoring ≠ Security So why is there an abundance of SPM vendors?
Because posture is easier.
- Easier to build. Cloud-only, read-only, event-driven. No need to support endpoints, on-prem, hybrid or inline enforcement. Just scan, analyze, alert.
- Easier to sell. No rip-and-replace. Posture tools bolt onto the existing stack, not replace it. That also means customers end up managing yet another vendor, another dashboard, another integration.
- Easier to adopt. No agents, low friction, fast time-to-value. Good enough to show progress, but not strong enough to stop attacks.
Yes, posture matters. But let’s not mistake issue tracking for actual security.
Security requires action — not just awareness.
False confidence, real consequencesThere’s an illusion of progress that posture tools can create. Dashboards look active. Tickets are assigned. Metrics suggest movement. But beneath that layer of perceived control, many organizations remain dangerously exposed.
In fact, {children}. Visibility alone isn’t moving the needle—security teams are still drowning in noise while real risks slip through. That's the difference between knowing something's wrong and doing something about it.
It’s why so many breaches still happen in environments that were “monitored.” The problem wasn’t a lack of alerts, it was the inability to respond in time.
And the results? Stolen IP. Leaked customer records. Compliance violations. Brand damage. Leadership churn.
The stakes aren’t theoretical. And yet too many teams are trapped in a cycle of detection without defense.
It’s time to rethink what protection meansThe right approach isn’t a patchwork of posture tools and point integrations. It’s a unified system — deep within a specific domain — that doesn’t just highlight problems but solves them in real time.
Whether you’re focused on data, identities or assets, true security means:
- Continuous classification of what’s sensitive: Modern DLP starts by building a living inventory of sensitive data — constantly discovering and labeling information across SaaS apps, endpoints, on-premise file shares and emails. It ensures you always know what you're protecting, even as your data changes and moves.
- Real-time monitoring of how it’s accessed and shared: Visibility into who’s touching your data, when, and how allows security teams to identify risky behavior instantly — not after the fact. This creates accountability and supports both proactive defense and forensic insight.
- Contextual enforcement that prevents misuse: It’s not enough to just watch. Real-time protection at the endpoint means applying intelligent controls based on business context — blocking or coaching users when behavior looks risky, not just flagging it.
- Automated remediation that closes the loop: When policies are violated, MIND acts. From revoking access and deleting shared links to educating users in near real time, the loop is closed automatically — without requiring tickets, escalations or delays.
This isn’t a wishlist. This is what modern DLP — done right — can and should deliver.
Enter MIND: Posture & PreventionThat’s what MIND was built to do.
MIND combines the context-aware insights of DSPM (posture) with the automated enforcement of modern DLP (prevention).
We help security teams move beyond alert fatigue to actual control. Beyond passive monitoring to meaningful action. Beyond fractured tools to full-spectrum protection.
Our AI-powered classification engine understands your data in context—whether it’s source code, contracts, financial records, credentials, passwords, or PII. And it enforces your policies wherever data lives: SaaS and Gen AI apps, endpoints, on-premise file shares, emails and beyond.
We don’t just surface issues. We solve them.We don’t just map risks. We mitigate them.
We don’t just warn you. We stop the leaks.
Security leaders are overburdened, not underinformed. With limited resources, increasing complexity and high expectations, they need solutions that deliver results, not just more dashboards.
Stop scanning. Start securing.
Mind What Matters.The post Posture ≠ Protection appeared first on Security Boulevard.
CVE-2005-4053 | coWiki 0.3.4 26.html cross site scripting (EDB-30515 / BID-25393)
Beware of Fake Booking.com Sites That Infects Your Devices With AsyncRAT
Cybercriminals have launched a sophisticated campaign targeting travelers through fake Booking.com websites that deploy AsyncRAT malware, according to recent security research. The threat actors redirect users from gaming sites, social media platforms, and sponsored advertisements to convincing replica booking sites designed to compromise visitor devices. This attack capitalizes on the fact that 40% of people […]
The post Beware of Fake Booking.com Sites That Infects Your Devices With AsyncRAT appeared first on Cyber Security News.
Царь умер, да здравствует выбор: Windows наконец делает то, что ты хочешь
CVE-2011-0104 | Microsoft Excel 2002/2003 memory corruption (EDB-35573 / Nessus ID 53374)
报告称 AI 的普及和增长“史无前例”
Photos: Infosecurity Europe 2025
Infosecurity Europe 2025 is a cybersecurity event taking place from June 3 to 5 in London. Help Net Security is on-site and here’s a closer look at the conference. The featured vendors are: Okta, PlexTrac, ISC2, Insight, EasyDMARC, Defense.com, Tines, Darktrace, Torq, and Cyrebro.
The post Photos: Infosecurity Europe 2025 appeared first on Help Net Security.
Только через 15 лет WhatsApp додумался до того, что есть в Telegram
CVE-2004-1962 | Protector System 1.15b1 Filters index.php sql injection (EDB-24047 / XFDB-15969)
Malicious NPM Packages Attacking Ethereum Wallets Using Obfuscated JavaScript
A sophisticated cryptocurrency theft campaign has emerged on the npm package registry, targeting developers and cryptocurrency users through malicious packages designed to drain Ethereum and Binance Smart Chain wallets. The attack leverages heavily obfuscated JavaScript code to steal up to 85% of victims’ cryptocurrency holdings, demonstrating an evolving threat landscape where software supply chain attacks […]
The post Malicious NPM Packages Attacking Ethereum Wallets Using Obfuscated JavaScript appeared first on Cyber Security News.
Interlock and the Kettering Ransomware Attack: ClickFix’s Persistence
In healthcare, every minute of downtime isn’t just a technical problem — it’s a patient safety risk.
CNN recently reported that Kettering Health, a major hospital network in Ohio, was hit by a ransomware attack. According to CNN, the Interlock ransomware group claimed responsibility, sending a chilling reminder that healthcare remains a prime target for this particular ransomware gang.
While technical details of the Kettering attack remain scarce, Interlock’s recent history — and the emergence of browser-based attack chains like ClickFix — should put every CISO on high alert. In fact, HHS released a sector-level alert on ClickFix, due to the severity of the attack and how focused attackers were in targeting healthcare organizations. Again, though it is not yet confirmed that this specific exploit was used at Kettering, Interlock has been linked to ClickFix attacks elsewhere.
While Kettering continues to focus on incident response, for those watching across the industry, what’s clear is the growing role of browser-based attacks in ransomware campaigns, and how, in healthcare environments, these kinds of attacks can be life-threatening.
Healthcare Remains a Top TargetRansomware actors continue to prioritize healthcare organizations as targets because of the high value placed on continuity of care. Timely access to records, imaging, and communication systems is essential for delivering treatment — so when those systems are disrupted, the operational impact is immediate.
Healthcare organizations are uniquely vulnerable to ransomware for several reasons:
- Dispersed and unmanaged endpoints: Clinicians often use shared workstations, personal laptops, and mobile devices, increasing attack surface.
- High uptime requirements: Any downtime can delay surgeries, diagnostics, or emergency care — forcing quick, sometimes quiet, ransom payments.
- Regulatory pressure: Standards and requirements like HIPAA and HITRUST turn data breaches and outages into costly, reportable incidents.
- High ROI for attackers: Medical data and patient information continues to be the most valuable information sold on the dark web
The stakes are high: In 2024, 67% of healthcare organizations reported a ransomware attack, and research shows that patient care delays increase measurably during major incidents.
Recent examples of healthcare organizations disrupted because of a cyberattack include:
- Change Healthcare (2024): Payment processor attack rippled across the U.S., delaying claims and payments for weeks.
- CommonSpirit Health (2022): 600,000+ patient records exposed, care delayed, millions in costs.
- Universal Health Services (2020): 250 facilities offline, staff forced to revert to paper, patient care disrupted.
As more clinical and operational workflows move into SaaS apps and browser-delivered interfaces, the browser itself is becoming more relevant to healthcare security.
Understanding ClickFix and Browser-Based TacticsClickFix is a technique that relies on seemingly legitimate browser interactions — like fake CAPTCHAs or pop-up prompts — to trick users into activating malicious scripts. What makes this approach difficult to detect is that it relies heavily on the browser for clipboard manipulation, with no file download to trigger traditional file-based alerts or network signatures.
Here’s how a ClickFix attack could unfold in a healthcare organization:
- A healthcare worker visits a compromised website or clicks a phishing link.
- A fake browser prompt appears (e.g., “Please complete this CAPTCHA to continue”).
- The user is tricked into copying and running a script (often a PowerShell command), which silently installs malware — sometimes without any download or obvious warning.
SquareX first detailed this technique in 2024 to illustrate a broader challenge: many endpoint and network tools lack visibility into what happens in the browser — including browser extensions, clipboard activity, and in-browser scripting.
🧠 Read our full analysis, with step-by-step details, of the ClickFix attack →
Why Traditional Security Tools Miss Browser AttacksMost healthcare organizations rely on a familiar stack: Secure Web Gateways (SWG), Endpoint Detection & Response (EDR), and Data Loss Prevention (DLP). But these tools were not designed for the complexity of modern browsers.
What they miss:
- DOM-level changes (malicious form injections or script manipulations)
- Malicious browser extensions (often installed by non-technical staff)
- Clipboard hijacking (stealing credentials or session tokens)
- Client-side file and data reassembly (a malicious file that is broken into parts to avoid detection and after all pieces are downloaded, it is reassembled into a full payload)
- WASM-based payloads (running near-native code inside the browser)
Meanwhile, many clinical workflows — from EHRs to claims portals — now run in the browser. In fact, a 2024 survey of the healthcare technology market showed healthcare SaaS expecting to grow nearly 20% by 2028.
This is where Browser Detection & Response (BDR) can complement existing investments — by providing client-side visibility into user behavior and web application interactions that traditional controls can’t see.
Practical Next Steps for Healthcare Security TeamsThis is a good moment to reassess browser-layer visibility and controls. Here are some actions that security teams can take today:
- Audit browser extension policies and usage, especially for unmanaged or personal devices accessing hospital systems.
- Review recent phishing incidents for browser-based interaction patterns — such as prompts, redirects, or spoofed logins.
- Test your existing tools against modern client-side attack scenarios. Tools like SquareX’s Web Security Posture Assessment offer a free analysis of your current risk based on real-world threats.
- Explore BDR solutions that can provide visibility into browser events, prevent data leakage, and enrich threat investigations — without disrupting clinical workflows.
The Kettering Health ransomware incident is yet another reminder of how persistent and creative today’s adversaries have become. While we don’t yet know exactly how the breach occurred, the involvement of a group known to use browser-based techniques raises thoughtful questions for defenders.
Rather than respond with alarm, this is an opportunity to ask:
Do we have the visibility we need at the browser layer?
Are we prepared to detect and respond to client-side threats that bypass legacy controls?
If your answer is no, that’s okay. Modernizing browser security doesn’t require a full overhaul — you may just need to layer in the right visibility where today’s users and workflows operate. Learn more in this Browser Detection and Response white paper.
Interlock and the Kettering Ransomware Attack: ClickFix’s Persistence was originally published in SquareX Labs on Medium, where people are continuing the conversation by highlighting and responding to this story.
The post Interlock and the Kettering Ransomware Attack: ClickFix’s Persistence appeared first on Security Boulevard.