blogmirnet – Page 4 – My information Resource (blog.mir.net)

NCCoE Cybersecurity Connections – Implementing a Zero Trust Architecture

Photo Credit: Shutterstock

Event Recording Now Available!

NCCoE Cybersecurity Connections Event

Last week, the National Cybersecurity Center of Excellence (NCCoE) hosted a Cybersecurity Connections Event and Networking Lunch focused on Implementing a Zero Trust Architecture.

Hosted in partnership with the Maryland Department of Commerce and Montgomery County, these quarterly events feature a discussion on cybersecurity best practices from leaders in the community as well as a networking lunch sponsored by the Montgomery County Economic Development Corporation on behalf of Montgomery County, Maryland.

Leaders from the NCCoE, Tenable, TechNuf LLC, and Cisco came together for a panel discussion focused on deploying zero trust architectures. Panelists exchanged views concerning key technology capabilities necessary to implement zero trust architectures, insider threats, automation, vulnerability and threat detection, as well as the current state of cybersecurity across government agencies.

The recording of this event is now available on the NCCoE event webpage.

Visit the NCCoE project page to learn more about our Zero Trust Architecture guidance. If you have any questions, please do not hesitate to contact us at [email protected].

View the Recording

Iranian Cyber Actors Targeting Critical Infrastructure Organizations Using Brute Force

The Federal Bureau of Investigation (FBI), the Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), the Communications Security Establishment Canada (CSE), Australian Federal Police (AFP), and Australian Signals Directorate’s Australian Cyber Security Centre (ASD’s ACSC) released this Joint Cybersecurity Advisory to warn network defenders of Iranian cyber actors’ use of brute force and other techniques to compromise organizations across multiple critical infrastructure sectors. The threat actors likely aim to obtain credentials and information describing the victim’s network that can then be sold to enable access to cybercriminals.

Since October 2023, Iranian actors have used brute force, such as password spraying, and multifactor authentication (MFA) ‘push bombing’ to compromise user accounts and obtain access to organizations. The actors frequently modified MFA registrations, enabling persistent access. The actors performed discovery on the compromised networks to obtain additional credentials and identify other information that could be used to gain additional points of access. The authoring agencies assess the Iranian actors sell this information on cybercriminal forums to actors who may use the information to conduct additional malicious activity

This advisory provides the threat actors’ tactics, techniques, and procedures (TTPs) and indicators of compromise (IOCs). The information is derived from FBI engagements with entities impacted by this malicious activity. The authoring agencies recommend critical infrastructure organizations follow the guidance provided in the mitigations section of this advisory. At a minimum, organizations should ensure all accounts use strong passwords and register a second form of authentication.

Security Property Verification by Transition Model | NIST publishes IR 8539

NIST Internal Report (IR) 8539, Security Property Verification by Transition Model, is now available.

Verifying the security properties of access control policies is a complex and critical task. Often, the policies and their implementation do not explicitly express their underlying semantics, which may be implicitly embedded in the logic flows of policy rules, especially when policies are combined. Instead of evaluating and analyzing access control policies solely at the mechanism level, formal transition models can describe these policies and prove the system’s security properties, ensuring that access control mechanisms are designed to meet security requirements.

This document explains how to apply model-checking techniques to verify security properties in transition models of access control policies. It provides a brief introduction to the fundamentals of model checking and demonstrates how access control policies are converted into automata from their transition models. The document also discusses property specifications in terms of linear temporal logic (LTL) and computation tree logic (CTL) languages with comparisons between the two. Finally, the verification process and available tools are described and compared.

Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution – PATCH: NOW

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. Google Chrome is a web browser used to access the internet. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLEGENCE:
There are currently no reports of these vulnerabilities being exploited in the wild

SYSTEMS AFFECTED:

Google Chrome versions prior to 132.0.6834.110/111 for Windows and Mac.
Google Chrome versions prior to 132.0.6834.110 for Linux.

RISK:
Government:

Large and medium government entities: High
Small government entities: Medium

Businesses:

Large and medium business entities: High
Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows:

Tactic: Initial Access (TA0001):
Technique: Drive-By Compromise (T1189):

Object Corruption in V8 resulting in heap corruption (CVE-2025-0611)
Out of bounds memory corruption in V8 resulting in heap corruption (CVE-2025-0612)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

Apply appropriate updates provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 9.1: Ensure Use of Only Fully Supported Browsers and Email Clients: Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.

Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.

Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)
Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
- Safeguard 9.2: Use DNS Filtering Services: Use DNS filtering services on all enterprise assets to block access to known malicious domains.
- Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
- Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.

Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources. Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. (M1017: User Training)
- Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.

REFERENCES:

Google:
https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_22.html

CVE:
https://www.cve.org/CVERecord?id=CVE-2025-0611
https://www.cve.org/CVERecord?id=CVE-2025-0612

Tax-Related Phishing Scams Now Deliver Malware

Last week, the NJCCIC reported increased phishing attempts targeting NJ state employees by impersonating the IRS. Proofpoint analysts noted a rise in tax-themed phishing campaigns, particularly as tax deadlines approach in the US and the UK. Likewise, these campaigns were also observed targeting NJ state employees. These phishing attempts typically impersonate government or financial organizations connected to tax filing. In early January, Proofpoint identified hundreds of malicious domains linked to tax-related campaigns, many of which impersonated legitimate companies.

Email impersonating Intuit (left); credential phishing landing page (right). Image Source: Proofpoint

One campaign observed on January 16 impersonated Intuit but used a generic sender with a URL directing users to a fake authentication page to harvest credentials. This campaign delivered 40,000 emails and impacted over 2,000 organizations.

Malicious email impersonating tax software. Image Source: Proofpoint

While most tax-themed campaigns typically focus on credential phishing, some were also observed delivering malware. A separate campaign impersonated a tax software company that distributed two malware payloads via a JavaScript file hosted on Microsoft Azure, leading to the deployment of Rhadamanthys malware and zgRAT. Additionally, various unrelated campaigns impersonating tax agencies and software have been observed attempting to deliver different malware payloads, including MetaStealer, XWorm, AsyncRAT, and VenomRAT.

Recommendations

Beware of communications claiming to be from the IRS.

The IRS does not contact individuals by phone, email, or text message to solicit information or money.

Instead, the IRS sends notices and bills through postal mail.

Facilitate user awareness training to include these types of phishing-based techniques.

Avoid clicking links, opening attachments, responding to, or acting on unsolicited text messages or emails.

Type official website URLs into browsers manually.

Ensure multi-factor authentication (MFA) is enabled for all online accounts.

Consider leveraging behavior-based detection tools rather than signature-based tools.

Technical details, TTPs, and indicators of compromise (IOCs) can be found in the Proofpoint blog post.

Report phishing emails and other malicious cyber activity to the FTC, FBI’s IC3, and the NJCCIC.

Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution – PATCH NOW

Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLEGENCE:
Apple is aware of a report that CVE-2025-24085 may have been actively exploited against versions of iOS before iOS 17.2.

SYSTEMS AFFECTED:

Versions prior to visionOS 2.3
Versions prior to iPadOS 17.7.4
Versions prior to iOS 18.3 and iPadOS 18.3
Versions prior to macOS Sequoia 15.3
Versions prior to macOS Sonoma 14.7.3
Versions prior to macOS Sequoia 15.3
Versions prior to macOS Ventura 13.7.3
Versions prior to watchOS 11.3
Versions prior to tvOS 18.3
Versions prior to Safari 18.3

RISK:
Government:

Large and medium government entities: High
Small government entities: Medium

Businesses:

Large and medium business entities: High
Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Details of the vulnerabilities are as follows:

Tactic: Execution (TA0002):

Technique: Exploitation for Client Execution (T1203):

A remote attacker may cause an unexpected application termination or arbitrary code execution. (CVE-2025-24137)
A malicious application may be able to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 17.2. (CVE-2025-24085)
An app may be able to execute arbitrary code with kernel privileges. (CVE-2025-24159)
An app with root privileges may be able to execute arbitrary code with kernel privileges. (CVE-2025-24153)
An app may be able to elevate privileges. (CVE-2025-24156)

Additional lower severity vulnerabilities include:

An attacker on the local network may be able to cause unexpected system termination or corrupt process memory. (CVE-2025-24126)
A remote attacker may cause an unexpected app termination. (CVE-2025-24129)
An attacker in a privileged position may be able to perform a denial-of-service. (CVE-2025-24131)
Parsing a file may lead to an unexpected app termination. (CVE-2025-24127, CVE-2025-24160, CVE-2025-24161, CVE-2025-24163, CVE-2025-24123, CVE-2025-24124, CVE-2025-24112, CVE-2025-24106)
Processing an image may lead to a denial-of-service. (CVE-2025-24086)
An app may be able to fingerprint the user. (CVE-2025-24117)
Processing maliciously crafted web content may lead to an unexpected process crash. (CVE-2025-24166, CVE-2025-24162, CVE-2024-54478)
Visiting a malicious website may lead to user interface spoofing. (CVE-2025-24113)
Parsing a file may lead to disclosure of user information. (CVE-2025-24149)
An attacker may be able to cause unexpected system termination or corrupt kernel memory. (CVE-2025-24154)
A maliciously crafted webpage may be able to fingerprint the user. (CVE-2025-24143)
Processing web content may lead to a denial-of-service. (CVE-2025-24158, CVE-2024-54497)
An app may be able to determine a user’s current location. (CVE-2025-24102)
An app may be able to cause unexpected system termination or write kernel memory. (CVE-2025-24118, CVE-2024-54509)
Restoring a maliciously crafted backup file may lead to modification of protected system files. (CVE-2025-24104)
An attacker with physical access to an unlocked device may be able to access Photos while the app is locked. (CVE-2025-24141)
A remote attacker may be able to cause a denial-of-service. (CVE-2025-24177)
A malicious app may be able to gain root privileges. (CVE-2025-24107)
An app may gain unauthorized access to Bluetooth. (CVE-2024-9956)
Visiting a malicious website may lead to address bar spoofing. (CVE-2025-24128)
An app may be able to view a contact’s phone number in system logs. (CVE-2025-24145)
Copying a URL from Web Inspector may lead to command injection. (CVE-2025-24150)
An app may be able to access protected user data. (CVE-2025-24087, CVE-2025-24103, CVE-2025-24108)
An app may be able to access information about a user’s contacts. (CVE-2025-24100)
An app may be able to access sensitive user data. (CVE-2025-24109)
An app may be able to modify protected parts of the file system. (CVE-2025-24114, CVE-2025-24121, CVE-2025-24122, CVE-2025-24130, CVE-2024-44243)
An app may be able to access user-sensitive data. (CVE-2025-24134, CVE-2025-24094, CVE-2025-24101)
Files downloaded from the internet may not have the quarantine flag applied. (CVE-2025-24140)
An app may be able to bypass Privacy preferences. (CVE-2025-24174, CVE-2025-24116)
An app may be able to read files outside of its sandbox. (CVE-2025-24115)
A malicious app may be able to create symlinks to protected regions of the disk. (CVE-2025-24136)
A malicious app may be able to access arbitrary files. (CVE-2025-24096)
A malicious app may be able to bypass browser extension authentication. (CVE-2025-24169)
Deleting a conversation in Messages may expose user contact information in system logging. (CVE-2025-24146)
Parsing a maliciously crafted file may lead to an unexpected app termination. (CVE-2025-24139)
An app may be able to cause unexpected system termination or corrupt kernel memory. (CVE-2025-24151, CVE-2025-24152)
A malicious application may be able to leak sensitive user information. (CVE-2025-24138)
A local attacker may be able to elevate their privileges. (CVE-2025-24176)
An app may be able to gain elevated privileges. (CVE-2025-24135)
An app may be able to read sensitive location information. (CVE-2025-24092)
An attacker may be able to cause unexpected app termination. (CVE-2025-24120)
An app may be able to access contacts. (CVE-2024-44172)
An app may be able to access removable volumes without user consent. (CVE-2025-24093)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
- Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
- Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
- Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.

Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
- Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
- Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassessbi-annually, or more frequently.
- Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
- Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
Block execution of code on a system through application control, and/or script blocking. (M1038:Execution Prevention)
- Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
- Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
- Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
- Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
- Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:

Multiple Vulnerabilities in SimpleHelp RMM Could Allow for Arbitrary Code Execution – PATCH NOW

Multiple vulnerabilities have been discovered in SimpleHelp RMM that could allow for arbitrary code execution. SimpleHelp is a popular remote access software. Successful exploitation of the most severe of these vulnerabilities when chained together could allow for remote code execution in the context of the system. Depending on the privileges associated with the system, an attacker could then install programs; view, change, or delete data. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLEGENCE:
Help Net Security has indicated the SimpleHelp RMM vulnerabilities may have been exploited to breach healthcare organizations.

SYSTEMS AFFECTED:

SimpleHelp v5.5
SimpleHelp v5.4
SimpleHelp v5.3

RISK:
Government:

Large and medium government entities: High
Small government entities: Medium

Businesses:

Large and medium business entities: High
Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in SimpleHelp RMM that could allow for arbitrary code execution. Details of the vulnerabilities is as follows:

Tactic: Initial Access (TA0001):

Technique: Exploit Public-Facing Application (T1190):

An unauthenticated path traversal vulnerability that could allow attackers to download arbitrary files from the SimpleHelp server, including logs and configuration secrets (encrypted with a hardcoded key) (CVE-2024-57727)

An arbitrary file upload flaw that could be exploited by authenticated attackers (e.g., leveraging admin credentials gleaned from downloading config files) to upload arbitrary files to the machine running the SimpleHelp server or even interact with/access remote machines if the unattended access option is switched on. For Linux servers, an attacker could exploit this vulnerability to upload a crontab file to execute remote commands. For Windows servers, an attacker could overwrite executables or libraries used by SimpleHelp to get to remote code execution. (CVE-2024-57728)
A vulnerability stemming from missing authorization checks for certain admin function could be misused by attackers to elevate their privileges to admin and, for example, exploit CVE-2024-57728 to take over the server. (CVE-2024-57726)

Successful exploitation of the most severe of these vulnerabilities when chained together could allow for remote code execution in the context of the system. Depending on the privileges associated with the system, an attacker could then install programs; view, change, or delete data. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:

We recommend the following actions be taken:

Apply appropriate updates provided by SimpleHelp to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.5 : Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
- Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.2: Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
- Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
- Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
- Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

REFERENCES:

SimpleHelp:
https://simple-help.com/kb—security-vulnerabilities-01-2025#security-vulnerabilities-in-simplehelp-5-5-7-and-earlier

Help Net Security:
https://www.helpnetsecurity.com/2025/01/16/critical-simplehelp-vulnerabilities-fixed-security-update-remote-support/

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57727
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57726
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57724

Recommendations for Key-Encapsulation Mechanisms | Draft SP 800-227 is Available for Comment

The initial public draft of NIST Special Publication (SP) 800-227, Recommendations for Key-Encapsulation Mechanisms, is now available for public comment.

NIST recently published Federal Information Process Standard (FIPS) 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard, to update its cryptographic standards with an algorithm designed to provide protection from quantum attacks. In addition, NIST will select one or two additional quantum-resistant key-encapsulation mechanisms (KEMs) for standardization. To provide guidance on using KEMs, NIST is introducing SP 800-227, Recommendations for Key-Encapsulation Mechanisms. This draft document describes the basic definitions, properties, and applications of KEMs. It also provides recommendations for implementing and using KEMs in a secure manner.

The public comment period is open through March 7, 2025. See the publication details for a copy of the draft and instructions for submitting comments.

NIST will also hold a virtual Workshop on Guidance for KEMs on February 25-26, 2025, to gather additional feedback on SP 800-227.

NIST Proposes to Revise SP 800-38B, “CMAC” and SP 800-38C, “CCM

In June 2024, NIST’s Crypto Publication Review Board initiated a review of the following publications:

NIST Special Publication (SP) 800-38B, Recommendation for Block Cipher Modes of Operation: the CMAC Mode for Authentication, 2016
SP 800-38C, Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality, 2007.

In response, NIST received public comments on SP 800-38B and SP 800-38C.

NIST proposes to revise both publications. The main technical changes would be the following:

Harmonize the tag length guidance in SP 800-38B with that of SP 800-38C (i.e., a minimum of 32 bits with a recommendation for at least 64 bits in general)
Strengthen the example formatting function for CCM to a requirement
Remove support for the disallowed Triple DES block cipher from CMAC

NIST would also consider other technical changes that were suggested in the public comments, in addition to editorial improvements.

Submit your comments on this decision proposal by February 28, 2025 to [email protected] with “Comments on SP 800-38B Decision Proposal” or “Comments on SP 800-38C Decision Proposal” in the subject line.

Comments received in response to this request will be posted on the Crypto Publication Review Project site after the due date. Submitters’ names and affiliations (when provided) will be included, while contact information will be removed. See the project site for additional information about the review process.

A Vulnerability in SonicWall Secure Mobile Access (SMA) 1000 Series Appliances Could Allow for Remote Code Execution – PATCH NOW

A vulnerability has been discovered in SonicWall Secure Mobile Access (SMA) 1000 Series Appliances which could allow for remote code execution. SonicWall Secure Mobile Access (SMA) is a unified secure access gateway used by organizations to provide employees access to applications from anywhere. Successful exploitation of this vulnerability could allow for remote code execution. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data.

THREAT INTELLEGENCE:
SonicWall PSIRT has been notified of possible active exploitation of the referenced vulnerability by threat actors.

SYSTEMS AFFECTED:

Version 12.4.3-02804 (platform-hotfix) and earlier versions.

RISK:
Government:

Large and medium government entities: High
Small government entities: Medium

Businesses:

Large and medium business entities: High
Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
A vulnerability has been discovered in SonicWall Secure Mobile Access (SMA) 1000 Series Appliances which could allow for remote code execution. Details of the vulnerability are as follows:

Tactic: Initial Access (TA0001):

Technique: Exploit Public-Facing Application (T1190):

Pre-authentication deserialization of untrusted data vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) and Central Management Console (CMC), which in specific conditions could potentially enable a remote unauthenticated attacker to execute arbitrary OS commands. (CVE-2025-23006)

RECOMMENDATIONS:

We recommend the following actions be taken:

Apply appropriate updates provided by SonicWall to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.5 : Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
- Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.2: Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
- Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.

Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.

Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
- Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.

Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
- Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.

Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

REFERENCES:

SonicWall:
https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2025-0002

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-23006