31Wedge

Source: BleepingComputer

Author: Lawrence Abrams

URL: https://www.bleepingcomputer.com/news/microsoft/microsoft-sharepoint-zero-day-exploited-in-rce-attacks-no-patch-available/

ONE SENTENCE SUMMARY:

A zero-day vulnerability in Microsoft SharePoint, CVE-2025-53770, has led to widespread exploitation, with ongoing efforts to mitigate and patch the issue.

MAIN POINTS:

1. Updated article reveals 54 organizations affected by SharePoint vulnerability.
2. CVE-2025-53770 has been exploited since July 18, affecting 85 servers.
3. Viettel’s “ToolShell” attack used chained SharePoint flaws CVE-2025-49706/49704.
4. Microsoft has not yet patched CVE-2025-53770; AMSI integration is recommended.
5. Enabling AMSI and Defender AV as mitigations prevent unauthenticated attacks.
6. SharePoint 2016/2019 updates include AMSI by default since September 2023.
7. Disconnect unprotected SharePoint servers to prevent exploitation.
8. CISA added CVE-2025-53770 to its Known Exploited Vulnerability catalog.
9. Over 29 organizations initially compromised, detected by Eye Security.
10. Attackers use “spinstall0.aspx” for MachineKey theft and RCE.

TAKEAWAYS:

1. Prompt application of upcoming SharePoint security patches is crucial.
2. Enabling AMSI and deploying Defender AV mitigates vulnerability risks.
3. Detecting specific IOCs can indicate compromised SharePoint servers.
4. Disconnect from the internet if unable to apply mitigations swiftly.
5. Monitoring for IP addresses associated with exploitation is essential.

Source: BleepingComputer

Author: Lawrence Abrams

URL: https://www.bleepingcomputer.com/news/security/citrix-bleed-2-exploited-weeks-before-pocs-as-citrix-denied-attacks/

ONE SENTENCE SUMMARY:

Citrix’s critical vulnerability “CitrixBleed 2” was exploited before public PoC release, prompting patch urgency and revealing transparency issues.

MAIN POINTS:

1. CVE-2025-5777, known as CitrixBleed 2, faced early exploitation despite no initial evidence claims by Citrix.
2. GreyNoise detected attacks from China beginning June 23, 2025, before PoC release.
3. Exploitation allowed attackers to extract sensitive data by manipulating login parameters.
4. Citrix was slow to acknowledge active exploitation and did not update advisories timely.
5. Security researcher Kevin Beaumont identified indicators of exploitation attempts in logs.
6. Misconfigured session terminations advised by Citrix may not fully prevent exploitation.
7. Over 120 companies compromised by the vulnerability as of June 2025.
8. Imperva reported 11.5 million attempts, with heavy targeting of the financial sector.
9. Citrix urged immediate patching of affected NetScaler versions for security.
10. No mitigations exist beyond patching; outdated versions need upgrading.

TAKEAWAYS:

1. Immediate patching is essential to protect systems against CVE-2025-5777.
2. Citrix’s advisory and communication processes need improvement for better transparency.
3. Monitoring specific log activities can help identify attempted exploitations early.
4. Organizations must address all session types for complete security.
5. Financial and other critical sectors need heightened vigilance due to targeted attacks.

Source: Medium

Author: Mehdi

URL: https://medium.com/@mpmab1/the-cake-guide-to-cyber-risk-quantification-understanding-lognormal-distributions-for-absolute-b31ee12daaa3

ONE SENTENCE SUMMARY:

This beginner’s guide explains lognormal distributions and their application in cyber risk quantification, using intuitive analogies and Python.

MAIN POINTS:

1. Lognormal distribution is essential in cyber risk quantification (CRQ).
2. Aimed at beginners without prior statistics knowledge.
3. Uses intuitive analogies like cake and cars.
4. Describes why averages are misleading in skewed data.
5. Explains transforming, validating, and reverse-transforming lognormal data.
6. Python and Monte Carlo simulations model cyber loss scenarios.
7. Visualize results with histograms and CDFs.
8. Lognormal properties: only positive, skewed, starts at zero, log is normal.
9. Misleading averages corrected by data transformation.
10. Applies to real-world scenarios like incomes and cyber losses.

TAKEAWAYS:

1. Averages in lognormal distributions can be misleading.
2. Log transformations stabilize data for better analysis.
3. Exponentiation returns data to its original scale.
4. Visualizing data helps to identify skewness and distribution types.
5. Monte Carlo simulations provide insights into possible outcomes.

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2025/07/cisco-warns-of-critical-ise-flaw.html

ONE SENTENCE SUMMARY:

A critical Cisco security vulnerability could allow unauthorized remote code execution in ISE systems, urging immediate patching and system updates.

MAIN POINTS:

1. New vulnerability affects Cisco ISE, allowing arbitrary code execution with root privileges.
2. Tracked as CVE-2025-20337 with a maximum CVSS score of 10.0.
3. Similar to CVE-2025-20281, recently patched.
4. Exploitable through crafted API requests due to insufficient input validation.
5. Kentaro Kawane credited with discovering the flaw.
6. Affects ISE versions 3.3 and 3.4, fixed in specific patches.
7. No current evidence of malicious exploitation of this vulnerability.
8. Related exploits in Fortinet FortiWeb are reportedly being used maliciously.
9. 77 FortiWeb instances compromised, primarily in North America, Asia, and Europe.
10. Censys reports 20,098 online FortiWeb appliances, with unknown vulnerability status.

TAKEAWAYS:

1. Patch ISE systems immediately to safeguard against CVE-2025-20337.
2. Ensure robust validation procedures for API inputs to prevent exploits.
3. Continually monitor security advisories for timely updates.
4. Stay informed of related exploits affecting similar systems like FortiWeb.
5. Regular system updates are crucial to minimize security threats.

Source: 7 obsolete security practices that should be terminated immediately | CSO Online

Author: unknown

URL: https://www.csoonline.com/article/4022848/7-obsolete-security-practices-that-should-be-terminated-immediately.html

ONE SENTENCE SUMMARY:

Modern security requires moving beyond outdated practices, emphasizing zero trust, user awareness, and adaptive strategies against evolving threats.

MAIN POINTS:

1. Perimeter-only security is inadequate for cloud-based, remote, and distributed environments.
2. Compliance-driven security prioritizes regulations over actual threat mitigation.
3. Legacy VPNs are inefficient and risky, needing replacement with modern solutions like SASE.
4. Sole reliance on EDR is insufficient against non-endpoint threats; broader strategies are needed.
5. SMS-based two-factor authentication is vulnerable to multiple attack vectors.
6. On-prem SIEMs lead to inefficiencies and need upgrading for cloud capability.
7. End users must transition from passive to active participants in security culture.
8. User education and empowerment are crucial to building strong security defenses.
9. Zero trust and CARTA are recommended for continuous threat monitoring.
10. Adversaries exploit trust relationships and technology gaps beyond traditional detection methods.

TAKEAWAYS:

1. Adopt zero-trust principles to enhance security across diverse work environments.
2. Move beyond compliance-driven security, focus on real threat management.
3. Replace legacy VPNs with secure, adaptive access solutions like SASE.
4. Enhance security practices beyond endpoint solutions like EDR.
5. Educate users to actively engage in security efforts, strengthening organizational defenses.

Source: Help Net Security

Author: Zeljka Zorz

URL: https://www.helpnetsecurity.com/2025/07/16/update-google-chrome-to-fix-actively-exploited-zero-day-cve-2025-6558/

ONE SENTENCE SUMMARY:

Google patched a critical Chrome zero-day vulnerability, CVE-2025-6558, actively exploited to escape the browser’s security sandbox.

MAIN POINTS:

1. CVE-2025-6558 is a high-severity vulnerability in Chrome’s ANGLE and GPU.
2. Incorrect input validation enables attackers to escape Chrome’s sandbox.
3. The flaw was reported by Google Threat Analysis Group researchers.
4. Attack requires users to visit a specially crafted HTML page.
5. Active exploitation suggests involvement of state-sponsored or mercenary actors.
6. Also patched: CVE-2025-7656 (V8 engine) and CVE-2025-7657 (WebRTC).
7. Affects Chrome for Windows, macOS, and Linux prior to v138.0.7204.157/.158.
8. Users are advised to update Chrome to the latest version promptly.
9. Other Chromium-based browsers are expected to receive similar updates.
10. Microsoft is preparing a similar fix for the Edge browser.

TAKEAWAYS:

1. Update Chrome to prevent exploitation of CVE-2025-6558.
2. The vulnerability underscores the importance of regular software updates.
3. Stay informed about security alerts for proactive protection.
4. Other browsers like Edge, Brave, Opera, and Vivaldi are implementing fixes.
5. Vigilance against specially crafted web content is crucial for security.

Source: TrustedSec

Author: Chris Camejo

URL: https://trustedsec.com/blog/hipaa-hitech-and-hitrust-its-high-time-to-make-sense-of-it-all

ONE SENTENCE SUMMARY:

HIPAA, HITECH, and HITRUST are interrelated frameworks ensuring healthcare organizations protect patient data and maintain compliance.

MAIN POINTS:

1. HIPAA sets national standards for protecting sensitive patient health information.
2. HITECH Act strengthens HIPAA by promoting electronic health records and increasing penalties for violations.
3. HITRUST provides a certifiable framework to help organizations meet HIPAA and HITECH requirements.
4. HIPAA compliance is mandatory for covered entities and business associates in healthcare.
5. HITECH incentivizes adoption of secure electronic health records while enforcing stricter data security.
6. HITRUST CSF combines HIPAA, HITECH, and other standards into a unified security framework.
7. HITRUST certification demonstrates proactive risk management and regulatory compliance.
8. HIPAA focuses on privacy and security rules for protected health information (PHI).
9. HITECH enhances enforcement and extends HIPAA responsibilities to third-party vendors.
10. HITRUST helps organizations streamline compliance efforts through standardized assessments.

TAKEAWAYS:

1. HIPAA is the foundational regulation for healthcare data privacy and security.
2. HITECH reinforces HIPAA with stronger enforcement and EHR adoption incentives.
3. HITRUST offers a practical path to demonstrate HIPAA and HITECH compliance.
4. Certification through HITRUST can reduce compliance complexity and increase trust.
5. Understanding all three frameworks ensures comprehensive data protection in healthcare environments.

Source: CQURE Academy

Author: Kate Chrzan

URL: https://cqureacademy.com/blog/65-ntlm-reflection-smb-flaw/

1. ONE SENTENCE SUMMARY: CVE-2025-33073 enables attackers to exploit legacy SMB protocols and coercion methods for full system compromise via NTLM relay.

2. MAIN POINTS:

3. SMB signing must be disabled on the target machine to allow authentication relay attacks.

4. The target must be vulnerable to coercion techniques like PetitPotam for exploitation to proceed.

5. Initial attack attempts without a DNS record fail due to inability to authenticate properly.

6. Adding a DNS record pointing to the attacker’s machine enables successful NTLM relay and SAM dump.

7. Changing the IP to the DNS record value allows the machine to relay authentication to itself.

8. LLMNR poisoning via Responder enables attacks without needing the DNS record.

9. Using impacket-ntlmrelayx with netexec and coerce_plus exploits the PrinterBug vulnerability.

10. Successful execution allows retrieval of local admin hash and local authentication.

11. Module LSA from netexec can be used to dump LSASS and gain further access.

12. The vulnerability highlights critical risks from legacy authentication protocols and misconfigurations.

13. TAKEAWAYS:

14. Disable SMB signing only if absolutely necessary, as it allows dangerous relay attacks.

15. Monitor and restrict DNS records to prevent abuse in authentication redirection.

16. Employ modern authentication mechanisms to mitigate legacy protocol exploitation.

17. Use tools like Responder and PetitPotam carefully during red team engagements or internal audits.

18. Regularly update systems and audit for coercion vulnerabilities like PrinterBug.

Source: Help Net Security

Author: Help Net Security

URL: https://www.helpnetsecurity.com/2025/07/14/microsoft-365-attack-surface/

1. ONE SENTENCE SUMMARY: Despite claiming advanced Microsoft 365 security, many organizations face frequent attacks due to misconfigurations, weak oversight, and misunderstood responsibilities.

2. MAIN POINTS:

3. 60% of organizations rate their Microsoft 365 security as strong, yet still suffer account compromise incidents.

4. Complexity from managing multiple tenants increases risk, with 78% of organizations using multi-tenant setups.

5. 49% of IT leaders incorrectly assume Microsoft backs up configurations automatically.

6. Misconfigurations and overlooked admin roles introduce serious vulnerabilities due to limited governance and visibility.

7. Organizations with 10+ tenants face 2.3x higher operational overhead compared to those with fewer tenants.

8. Only 20% of organizations have over 10 global admins, aligning with best practices.

9. 51% of organizations have over 250 Entra apps with read-write permissions, posing significant security risks.

10. 16% have no app permission oversight; most rely on manual or inadequate tools.

11. 68% of organizations face frequent Microsoft 365 access attempts by attackers.

12. Only 41% of organizations have effectively implemented MFA, despite its proven effectiveness in preventing breaches.

13. TAKEAWAYS:

14. Declaring strong security doesn’t equate to actual protection—oversight and enforcement are critical.

15. Multi-tenant architecture adds complexity, necessitating robust management and governance frameworks.

16. Many organizations neglect to back up configurations, exposing them to disaster recovery failures.

17. MFA is underutilized despite its proven ability to prevent 99.9% of account compromises.

18. Formal change control and disaster recovery plans significantly reduce misconfiguration and operational disruptions.

Source: Help Net Security

Author: Mirko Zorz

URL: https://www.helpnetsecurity.com/2025/07/09/why-cybersecurity-friction/

1. ONE SENTENCE SUMMARY: Internal cybersecurity friction, driven by complex tools, unclear processes, and cautious culture, hinders security teams more than external threats.

2. MAIN POINTS:

3. Security teams face internal friction due to tool sprawl, unclear ownership, and rigid processes.

4. Disconnected tools require analysts to switch dashboards, slowing response and increasing alert fatigue.

5. Approval-heavy workflows delay incident response, risking critical containment windows.

6. Lack of context in access requests leads to repeated clarification cycles, wasting time.

7. Ambiguities in responsibilities cause delays and confusion during handoffs between teams.

8. Caution culture discourages initiative, pushing decisions upward and reducing overall team agility.

9. Burnout and normalized inefficiencies lower morale and inhibit improvement efforts.

10. Evolving security roles now require balancing protection with enabling business growth.

11. Integration and shared data visibility can reduce both friction and risk.

12. Clear thresholds and role clarity empower faster, accountable responses without sacrificing security.

13. TAKEAWAYS:

14. Streamlining tools and processes can significantly improve security team efficiency and morale.

15. Trust frameworks and role clarity reduce the need for excessive approvals.

16. Culture change must promote speed and responsibility, not just caution.

17. Shared visibility and system-level enforcement reduce manual friction.

18. Internal delays are a silent threat that can undermine security more than external attacks.

Source: Unit 42

Author: Haizhou Wang, Ashkan Hosseini, Ashutosh Chitwadgi

URL: https://unit42.paloaltonetworks.com/lnk-malware/

1. ONE SENTENCE SUMMARY: Attackers increasingly exploit Windows LNK files, using varied techniques such as exploits, malicious file execution, and embedded scripts for malware delivery.

2. MAIN POINTS:

3. Malicious LNK samples surged from 21,098 in 2023 to 68,392 in 2024.

4. LNK files act as shortcuts to other files, applications, or folders in Windows.

5. Attackers abuse LNK flexibility, disguising malware as legitimate files to trick users.

6. Four types of LNK malware: exploit execution, malicious file execution, in-argument scripts, and overlay content execution.

7. Most malicious LNK files contain LINKTARGET_IDLIST, RELATIVE_PATH, or COMMAND_LINE_ARGUMENTS structures.

8. Common system targets abused include powershell.exe, cmd.exe, rundll32.exe, conhost.exe, and mshta.exe.

9. COMMAND_LINE_ARGUMENTS can embed malicious scripts directly within LNK files.

10. Overlay content execution techniques involve find/findstr, mshta, or PowerShell commands.

11. CVE-2010-2568 vulnerability is notably exploited using corrupted LNK binaries.

12. Users should carefully inspect LNK file properties, especially target paths, to detect malware.

13. TAKEAWAYS:

14. Windows users should be cautious and verify LNK files’ properties before execution.

15. Cybersecurity teams must understand LNK malware techniques to enhance defenses.

16. Palo Alto Networks products offer protection against various LNK-based attacks.

17. Overlay content execution techniques are increasingly used to hide malicious payloads.

18. Awareness of common system targets and malware structures significantly aids malware detection.

Source: Help Net Security

Author: Help Net Security

URL: https://www.helpnetsecurity.com/2025/07/04/ntlm-relay-attacks/

ONE SENTENCE SUMMARY: NTLM relay attacks remain prevalent, simple to execute, and effective at compromising Active Directory environments, requiring proactive mitigation strategies.

MAIN POINTS:

1. NTLM relay attacks exploit authentication exchanges without needing password cracking or weak passwords.
2. Relay attacks often combine with authentication coercion techniques like Printer Bug or PetitPotam.
3. SMB servers, LDAP/LDAPS services, and ADCS web enrollment are primary NTLM relay targets.
4. SMB relay attacks can grant attackers access to sensitive shares and enable lateral movement.
5. LDAP relay attacks exploit unenforced LDAP signing and channel binding on domain controllers.
6. ADCS web enrollment relay attacks enable attackers to impersonate victims using malicious certificates.
7. Microsoft is introducing mitigations such as enforced SMB signing and LDAP sealing starting Windows Server 2025.
8. NTLM is still widely used due to legacy software hard-coded to use it instead of Kerberos.
9. Default configurations often leave older Windows environments highly vulnerable to relay attacks.
10. Enforcing signing, channel binding, and regularly evaluating environments are critical for defense.

TAKEAWAYS:

1. NTLM relay attacks remain a significant threat, commonly used in real-world attacks.
2. Authentication coercion makes relay attacks viable anytime, not relying on victim-initiated authentication.
3. Default configurations leave many organizations vulnerable; proactive changes are necessary.
4. Upcoming Windows Server 2025 security defaults will help, but organizations shouldn’t wait to implement mitigations.
5. Regular security evaluations, SMB/LDAP signing enforcement, and channel binding are essential defensive practices.

Source: Secure by Choice

Author: Sarah Aalborg

URL: https://securebychoice.com/blog/108175-we-see-what-we-expect-and-miss-what

ONE SENTENCE SUMMARY: Forensic investigations are impacted by cognitive biases like confirmation and anchoring, requiring deliberate strategies to mitigate their influence effectively.

MAIN POINTS:

1. Forensic analysis, despite being data-driven, is heavily influenced by cognitive biases.
2. Human brains naturally create stories, filtering new data through existing assumptions.
3. Confirmation bias leads investigators to focus only on evidence supporting initial theories.
4. Anchoring bias causes undue emphasis on the first piece of evidence discovered.
5. A Guardian-cited study found forensic experts influenced by contextual biases reached differing conclusions.
6. Bias affects even highly experienced experts, often without their awareness.
7. Explicitly naming biases can help teams recognize and counteract their impact.
8. Conducting pre-mortems encourages consideration of alternative hypotheses before deep investigation.
9. Introducing fresh perspectives can reduce anchoring effects and improve investigative accuracy.
10. Tracking multiple scenarios and reflecting on assumptions enhances learning and accuracy in forensics.

TAKEAWAYS:

1. Recognize that even expert investigators are vulnerable to cognitive biases.
2. Explicitly acknowledging biases helps mitigate their negative impact.
3. Regularly question initial assumptions and entertain multiple theories.
4. Seek input from individuals not influenced by initial investigative contexts.
5. Reflecting systematically on investigative processes improves future outcomes.

Source: BleepingComputer

Author: Sergiu Gatlan

URL: https://www.bleepingcomputer.com/news/security/cisco-removes-unified-cm-callManager-backdoor-root-account/

1. ONE SENTENCE SUMMARY: Cisco has patched a critical backdoor vulnerability (CVE-2025-20309) in Unified Communications Manager allowing attackers remote root access.

2. MAIN POINTS:

3. Cisco Unified CM had a critical backdoor root account vulnerability identified as CVE-2025-20309.

4. The vulnerability arises from static, default credentials used during development and testing.

5. CVE-2025-20309 affects Unified CM and SME Engineering Special releases 15.0.1.13010-1 to 15.0.1.13017-1.

6. Exploitation allows unauthenticated attackers root-level remote access to affected systems.

7. No workarounds exist; admins must upgrade or apply the CSCwp27755 security patch.

8. Cisco provided indicators of compromise to assist detection and response efforts.

9. Successful exploitation creates log entries under /var/log/active/syslog/secure accessible by admins.

10. Cisco previously experienced similar backdoor vulnerabilities in IOS XE, DNA Center, and Emergency Responder.

11. Earlier this year, Cisco patched similar issues in Smart Licensing Utility and IOS XE devices.

12. No current evidence indicates active exploitation or available proof-of-concept code online.

13. TAKEAWAYS:

14. Immediately apply the Cisco-provided security patch or upgrade to mitigate this severe vulnerability.

15. Regularly check logs at /var/log/active/syslog/secure for suspicious root user activities.

16. Stay vigilant for security advisories from Cisco regarding hardcoded credential vulnerabilities.

17. Maintain awareness that even reputable products may have hidden backdoor accounts.

18. Prioritize patch management to rapidly address high-severity vulnerabilities in critical infrastructure.

Source: Blog RSS Feed

Author: Gilad David Maayan

URL: https://www.tripwire.com/state-of-security/critical-security-risks-facing-cobol-mainframes

1. ONE SENTENCE SUMMARY: COBOL remains vital in global enterprise systems yet faces significant security risks requiring proactive measures and modern security practices.

2. MAIN POINTS:

3. COBOL is deeply embedded in critical global systems like banking, insurance, and government.

4. Legacy COBOL systems face growing cybersecurity threats due to outdated security configurations.

5. COBOL’s stability and batch processing efficiency sustain its widespread use in mainframe environments.

6. Industries relying on COBOL include finance, insurance, government, retail, manufacturing, and healthcare.

7. Dynamic SQL in COBOL applications can lead to SQL injection attacks if input isn’t sanitized.

8. Legacy communication protocols (FTP, TN3270) transmit sensitive data without encryption, increasing vulnerability.

9. Weak authentication and outdated access control methods expose COBOL systems to unauthorized access risks.

10. Privilege escalation vulnerabilities arise from poor application logic, misconfigurations, or insecure scripts.

11. COBOL applications often lack adequate input validation and error handling, risking exploitation.

12. Best practices include regular code reviews, pentesting, proactive patching, developer training, and compliance adherence.

13. TAKEAWAYS:

14. Regularly review and update legacy COBOL code to address potential vulnerabilities.

15. Employ comprehensive mainframe penetration testing to identify hidden security weaknesses.

16. Implement proactive patch management strategies to protect against known threats.

17. Provide ongoing developer training on secure coding practices specific to COBOL environments.

18. Ensure strict adherence to industry compliance standards for maintaining secure COBOL-based systems.

Source: Windows Incident Response

Author: Unknown

URL: http://windowsir.blogspot.com/2025/06/program-execution-follow-up-pt-ii.html

ONE SENTENCE SUMMARY: Validating program execution through multiple correlated data sources is crucial, rather than assuming artifacts alone indicate successful execution.

MAIN POINTS:

1. ShimCache and AmCache artifacts alone do not reliably indicate successful program execution.
2. Security Event Log (4720) confirms successful creation of user accounts beyond just command execution.
3. “net user” commands may inaccurately imply new account creation when only password is changed.
4. Application Event Log MsiInstaller records confirm actual installations via msiexec.exe.
5. Application Pop-up or Windows Error Reporting logs can show unsuccessful program launches.
6. Antivirus logs indicate if threats were successfully quarantined or if malware execution continued.
7. WMI-Activity/5861 event logs confirm successful creation of malicious WMI event consumers.
8. Parsing Objects.DATA file can verify if malicious event consumers persist in the WMI repository.
9. Correlating multiple data sources provides a system-level confirmation of actual execution outcomes.
10. Validating findings prevents incorrect decisions and ensures accurate resource allocation.

TAKEAWAYS:

1. Always validate artifact interpretations with complementary log sources.
2. Single artifacts alone rarely indicate successful execution; cross-reference multiple logs.
3. Consider transient and persistent data sources when confirming program execution.
4. Build timelines from multiple event logs to accurately validate threat actor actions.
5. Ensure your analysis is robust and data-supported, as critical decisions depend on accurate findings.

Source: BleepingComputer

Author: Lawrence Abrams

URL: https://www.bleepingcomputer.com/news/security/microsoft-365-direct-send-abused-to-send-phishing-as-internal-users/

1. ONE SENTENCE SUMMARY: A phishing campaign exploiting Microsoft 365’s Direct Send feature bypasses security measures, targeting numerous U.S. organizations to steal credentials.

2. MAIN POINTS:

3. Phishing attacks exploit Microsoft 365’s Direct Send, bypassing standard authentication and email security protocols.

4. Direct Send enables unauthenticated email delivery via a tenant’s smart host, designed for devices like printers.

5. Microsoft advises using Direct Send only if companies can properly manage and configure email servers.

6. Varonis MDDR team discovered the phishing campaign targeting over 70 U.S. organizations since May 2025.

7. Attackers primarily target financial services, manufacturing, healthcare, insurance, construction, and engineering sectors.

8. Phishing emails impersonate voicemail or fax notifications, including PDF attachments branded with company logos.

9. PDFs instruct victims to scan QR codes, redirecting them to fake Microsoft login pages for credential theft.

10. Attackers utilize PowerShell scripts sent from external IP addresses to send internal-looking emails.

11. Emails fail SPF, DKIM, DMARC checks yet pass through security as trusted internal traffic via smart host.

12. Microsoft introduced “Reject Direct Send” setting in Exchange Admin Center to mitigate these phishing attacks.

13. TAKEAWAYS:

14. Carefully evaluate if Direct Send is necessary, and if not, disable or restrict it immediately.

15. Enable “Reject Direct Send” in Exchange Online to prevent unauthorized internal-looking emails.

16. Implement strict DMARC policies (p=reject) to block unauthorized internal domain usage.

17. Train employees regularly to recognize and avoid phishing attempts, especially those involving QR codes.

18. Regularly monitor internal email traffic for signs of spoofing or abnormal behavior.

Source: BleepingComputer

Author: Bill Toulas

URL: https://www.bleepingcomputer.com/news/security/new-citrixbleed-2-netscaler-flaw-let-hackers-hijack-sessions/

1. ONE SENTENCE SUMMARY: Citrix warns of critical “CitrixBleed 2” vulnerabilities affecting NetScaler ADC and Gateway devices, potentially exposing sensitive user data.

2. MAIN POINTS:

3. Citrix disclosed vulnerabilities CVE-2025-5777 and CVE-2025-5349 affecting NetScaler ADC and Gateway devices.

4. CVE-2025-5777 is an out-of-bounds memory read allowing unauthenticated attackers memory access.

5. Vulnerable configurations include Gateway setups like VPN virtual servers, ICA Proxy, CVPN, and AAA servers.

6. Cybersecurity researcher named flaw “CitrixBleed 2” due to similarities with older CitrixBleed vulnerability.

7. Attackers exploiting CVE-2025-5777 could hijack sessions, bypass MFA, and access sensitive credentials.

8. CVE-2025-5349 involves improper access control in NetScaler Management Interface through various IPs.

9. Citrix recommends updating to safe versions: 14.1-43.56, 13.1-58.32, 13.1-NDcPP 13.1-37.235 (FIPS), and 12.1-55.328 (FIPS).

10. Admins should terminate all active ICA and PCoIP sessions after installing patches.

11. End-of-life versions ADC/Gateway 12.1 (non-FIPS) and ADC/Gateway 13.0 will not receive patches.

12. Over 56,500 publicly exposed NetScaler endpoints exist, unclear how many remain vulnerable.

13. TAKEAWAYS:

14. Immediately update NetScaler ADC and Gateway devices to mitigate “CitrixBleed 2” vulnerabilities.

15. Regularly monitor and terminate suspicious ICA and PCoIP sessions post-update.

16. Replace unsupported end-of-life versions promptly to maintain security posture.

17. Assess publicly exposed NetScaler endpoints to prioritize patching vulnerable systems.

18. Leverage automation to simplify and accelerate patch management processes.

Source: Dark Reading

Author: Fahmida Y. Rashid

URL: https://www.darkreading.com/endpoint-security/nist-outlines-real-world-zero-trust-examples

ONE SENTENCE SUMMARY: NIST’s new SP 1800-35 guidance provides practical examples and phased implementation strategies for organizations adopting end-to-end zero-trust architectures.

MAIN POINTS:

1. NIST released SP 1800-35 guidance demonstrating real-world zero-trust architectures using commercial technologies.
2. The guidance includes 19 practical example implementations developed over four years with 24 industry partners.
3. SP 1800-35 builds upon NIST SP 800-207, moving from conceptual to practical ZTA implementation advice.
4. Organizations must customize zero-trust deployments due to their unique network environments and security requirements.
5. Zero-trust architectures continuously evaluate and verify access requests, removing implicit trust in users or devices.
6. Implementing zero trust significantly reduces lateral movement and privilege escalation by malicious actors.
7. NCCoE team installed, configured, and tested each example, providing troubleshooting assistance and best practices.
8. Guidance aligns solutions with NIST Cybersecurity Framework and NIST SP 800-53 standards.
9. Organizations should incrementally adopt foundational elements like identity management and multifactor authentication.
10. Zero trust is an ongoing journey requiring continual adaptation to evolving threats, technologies, and organizational needs.

TAKEAWAYS:

1. Leverage NIST’s practical examples to start customized zero-trust deployments.
2. Begin ZTA implementation with a thorough inventory of existing organizational assets and capabilities.
3. Formulate clear access policies based on least privilege and continuous verification principles.
4. Incrementally implement ZTA components, starting with foundational security solutions.
5. Continuously monitor and evolve zero-trust architectures to address changing threats and business requirements.