Register for the 5th High-Performance Computing Security Workshop Registration deadline: April 30, 2025 ![]() High-performance computing (HPC) systems provide fundamental computing infrastructure and play a pivotal role in economic competitiveness and scientific discovery. Security is an essential component of HPC. NIST HPC Security Working Group (WG) has been leading the effort to create comprehensive and reliable security guidance for HPC systems. As part of the Working Group mission and to reach the greater HPC scientific community, NIST, in collaboration with the National Science Foundation (NSF), will host the 5th High-Performance Computing Security Workshop on May 7-8, 2025. The workshop aims to listen to the community’s needs and feedback, report and reflect on the ongoing activities at HPC Security WG, and define and discuss future directions with stakeholders from industry, academia, and government. For more information on the workshop, a list of speakers, and hotel information, please visit the event page. In-Person Registration fee: $200/person. Fee includes morning/afternoon snacks and lunch. Virtual Registration fee: $46/person In-Person Registration closes on April 30, 2025. Virtual attendee registration closes on May 8, 2025. Click on the button below to register. Register Now |
Vulnerability in Trimble Cityworks
A vulnerability has been discovered in Trimble Cityworks that could allow for remote code execution. Trimble Cityworks is a system that helps manage the lifecycle of assets for public infrastructure. It uses GIS (geographic information systems) to help with tasks such as permitting, licensing, construction, maintenance, and replacement. Successful exploitation of this vulnerability could allow for remote code execution in the context of the system. Depending on the privileges associated with the system, threat actors could then install programs or 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 Intelligence The Cybersecurity and Infrastructure Security Agency (CISA) reports CVE-2025-0994 has been exploited in the wild. |
Systems Affected |
Cityworks: All versions prior to 15.8.9 Cityworks with office companion: All versions prior to 23.10 |
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 |
Recommendations |
Apply appropriate updates provided by Trimble to vulnerable systems immediately after appropriate testing. 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. Use vulnerability scanning to find potentially exploitable software vulnerabilities to remediate them. 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. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. |
Register now: Microsoft 365 Copilot Training for IT
Join us at Microsoft 365 Copilot Training for IT to learn how to use Microsoft Copilot to simplify your everyday tasks. During this free event, discover how Copilot can help you enhance efficiency, simplify complex tasks, and optimize technical workflows. You’ll be able to: Use Copilot to summarize the information in a product spec document for a network security product and create a project plan to implement the product. Use Copilot in PowerPoint to create and customize a business presentation based on the product plan that you created for the new network security product. Use Copilot in Word to modify a technical implementation report for a customer who is planning to install your new network security product. Use Copilot in Outlook to draft an email that provides highlights from the technical implementation report that you created for the customer who is installing your new network security product. Join us at an upcoming event: Delivery Language: English Closed Captioning Language: English Event Delivery: Digital Microsoft Events – Microsoft 365 Copilot Training for IT |
Keyboard Shorts
Yes I still use shortcuts to make my life easy when running Windows computers and here is a guide for you.

Zyxel security advisory for command injection and insecure default credentials vulnerabilities in certain legacy DSL CPE
CVEs: CVE-2024-40890, CVE-2024-40891, CVE-2025-0890
Summary
Zyxel recently became aware of CVE-2024-40890 and CVE-2024-40891 being mentioned in a post on GreyNoise’s blog. Additionally, VulnCheck informed us that they will publish the technical details regarding CVE-2024-40981 and CVE-2025-0890 on their blog. We have confirmed that the affected models reported by VulnCheck, VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, are legacy products that have reached end-of-life (EOL) for years. Therefore, we strongly recommend that users replace them with newer-generation products for optimal protection.
What are the vulnerabilities?
CVE-2024-40890
**UNSUPPORTED WHEN ASSIGNED**
A post-authentication command injection vulnerability in the CGI program of certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, could allow an authenticated attacker to execute operating system (OS) commands on an affected device by sending a crafted HTTP POST request. It is important to note that WAN access is disabled by default on these devices, and this attack can only be successful if user-configured passwords have been compromised.
CVE-2024-40891
**UNSUPPORTED WHEN ASSIGNED**
A post-authentication command injection vulnerability in the management commands of certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500. This vulnerability could allow an authenticated attacker to execute OS commands on an affected device via Telnet. It is important to note that WAN access and the Telnet function are disabled by default on these devices, and this attack can only be successful if the user-configured passwords have been compromised.
CVE-2025-0890
**UNSUPPORTED WHEN ASSIGNED**
Insecure default credentials for the Telnet function in certain legacy DSL CPE models, including VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500, could allow an attacker to log in to the management interface if the administrators have the option to change the default credentials but fail to do so. It is important to note that WAN access and the Telnet function are disabled by default on these devices.
What should you do?
The following models—VMG1312-B10A, VMG1312-B10B, VMG1312-B10E, VMG3312-B10A, VMG3313-B10A, VMG3926-B10B, VMG4325-B10A, VMG4380-B10A, VMG8324-B10A, VMG8924-B10A, SBG3300, and SBG3500—are legacy products that have reached EOL status for several years. In accordance with industry product life cycle management practices, Zyxel advises customers to replace these legacy products with newer-generation equipment for optimal protection. If you obtained your Zyxel product through an internet service provider (ISP), please contact the ISP for support. For ISPs, please contact your Zyxel sales or service representatives for further details.
Additionally, disabling remote access and periodically changing passwords are proactive measures that can help prevent potential attacks.
Got a question?
If you are an ISP, please contact your Zyxel sales or service representative for further information or assistance. For customers who acquired your Zyxel device from an ISP, please reach out to the ISP’s support team directly.
Coordinated Timeline:
- 2024-07-13: VulnCheck notified Zyxel about vulnerabilities in the EOL CPE VMG4325-B10A without providing any reports.
- 2024-07-14: Zyxel requested VulnCheck to provide a detailed report; however, VulnCheck did not respond.
- 2024-07-31: VulnCheck published CVE-2024-40890 and CVE-2024-40891 on their blog without informing Zyxel.
- 2025-01-28: GreyNoise published CVE-2024-40890 and CVE-2024-40891 on their blog.
- 2025-01-29: Zyxel received VulnCheck’s report regarding CVE-2024-40890, CVE-2024-40891, and CVE-2025-0890.
- 2025-01-29: Zyxel became aware of the vulnerabilities in certain legacy DSL CPE models.
Revision history
2025-2-4: Initial release
Multiple Vulnerabilities in Google Android OSCould Allow for Privilege Escalation
This Multi-State Information Sharing and Analysis Center (MS-ISAC) Advisory is being provided to assist agencies, organizations, and individuals in guarding against the persistent malicious actions of cybercriminals. |
Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation in the context of the affected component. Depending on the privileges associated with the exploited component, threat actors could then install programs; view, change, or delete data; or create new accounts with full rights. |
Threat Intelligence There are indications that CVE-2024-53104 may be under limited, targeted exploitation. |
Systems Affected |
Android OS patch levels prior to 2025-02-05 |
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 |
Recommendations |
Apply appropriate mitigations provided by Google to vulnerable systems immediately after appropriate testing. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. Restrict execution of code to a virtual environment on or in transit to an endpoint system. |
Reference Android: https://source.android.com/docs/security/bulletin/2025-02-01 |
Reporting The NJCCIC encourages recipients who discover signs of malicious cyber activity to contact the NJCCIC via the cyber incident report form at www.cyber.nj.gov/report. |
Don’t Miss Out: Migrate to Innovate—Be AI-Ready, Be Secure
Tuesday, February 11, 2025 2:00 PM Eastern Time / 11:00 AM Pacific Time Digital Event Join us for a free Microsoft Discovery Hour to learn how migrating your IT estate to Microsoft Azure can prepare your organization for the AI era. Discover how Azure’s purpose-built solutions can help you optimize costs, boost performance, and provide the flexibility needed to achieve your goals. During this event, you’ll gain insights on: Azure’s comprehensive, multilayered approach to security. The adaptive cloud approach that meets you wherever you are in your cloud journey How Azure is designed to maximize your organization’s ROI and productivity Register today to prepare your organization with cutting-edge AI tools and optimize your IT estate for enhanced security and performance. |
Register here |
Microsoft Discovery Hour: Migrate to Innovate—Be AI-Ready, Be Secure |
Get your business ready for Microsoft 365 Copilot
Adapt your skills and master essential tools to excel in an AI-powered world at a free Microsoft 365 Virtual Training Day from Microsoft Learn. Join us at Prepare Your Organization for Microsoft 365 Copilot to learn about design features and deployment strategies. Discover how Copilot uses large language models with your work data—such as calendars, emails, chats, documents, and meetings—to enhance organization and productivity. Learn how Copilot capabilities boost creativity, productivity, and skills with real-time intelligent assistance across Microsoft 365 apps, including Word, Excel, PowerPoint, Outlook, Teams, and standalone chat experiences. Review the key elements of Copilot, understand its functionality, and explore ways to extend its capabilities. Additionally, gain insights into implementation steps, data preparation, and strategies for driving adoption and impact. You’ll have the opportunity to: Become familiar with the key components and capabilities of Microsoft 365 Copilot. Understand what your organization needs to implement Copilot successfully. Learn how to prepare your organization’s Microsoft 365 data for Copilot searches. Explore strategies for measuring and driving Copilot usage, adoption, and impact. Chat with Microsoft experts—ask questions and get answers to common challenges related to building real-time intelligent assistance into your Microsoft 365 apps. Join us at an upcoming Prepare Your Organization for Microsoft 365 Copilot event: February 18, 2025 11:00 AM – 1:30 PM | (GMT-06:00) Central Time US & Canada 12:00 PM – 2:30 PM | (GMT-05:00) Eastern Time US & Canada 10:00 AM – 12:30 PM | (GMT-07:00) Mountain Time US & Canada 9:00 AM – 11:30 AM | (GMT-08:00) Pacific Time US & Canada Delivery Language: English Closed Captioning Language(s): English Visit the Microsoft Virtual Training Days website to learn more about other event opportunities. |
Comment Period Extended | NIST Genomic Data Cybersecurity Publication
The NIST National Cybersecurity Center of Excellence (NCCoE) has released a draft publication to help organizations address cybersecurity threats associated with processing genomic data. The public comment period for the draft has been extended to Friday, February 14, 2025.
About the Draft
Draft NIST Cybersecurity White Paper (CSWP) 35, Cybersecurity Threat Modeling the Genomic Data Sequencing Workflow, evaluates potential threats in a genomic data processing environment using an iterative methodology. It provides an example use case that organizations can adapt to identify cybersecurity threats and apply mitigations in their environments.
While this paper focuses on cybersecurity threats, follow-on work includes privacy modeling for genomic data workflows and development of a Privacy Enhancing Technologies (PETs) testbed for privacy-preserving federated learning (PPFL).
We Want to Hear from You!
We welcome your feedback to help improve this publication. The public comment period for the draft is now open until 11:59 PM (ET) on Friday, February 14, 2025. More details for providing public feedback are within the draft.
Multiple Vulnerabilities in Google Android OS Could Allow for Privilege Escalation- PATCH: NOW
Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation in the context of the affected component. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
THREAT INTELLIGENCE:
There are indications that CVE-2024-53104 may be under limited, targeted exploitation
SYSTEMS AFFECTED:
- Android OS patch levels prior to 2025-02-05
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 Android OS, the most severe of which could allow for privilege escalation in the context of the affected component. Details of the vulnerabilities are as follows:
Tactic: Privilege Escalation (TA0004):
Technique: Exploitation for Privilege Escalation (T1068):
· Multiple vulnerabilities in Framework that could allow for escalation of privilege(CVE-2024-49721, CVE-2024-49743, CVE-2024-49746, CVE-2025-0097, CVE-2025-0098, CVE-2025-0099).
· A vulnerability in Platform that could allow for escalation of privilege. (CVE-2025-0094)
· Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2025-0091, CVE-2025-0095, CVE-2025-0096)
· Multiple vulnerabilities in Kernel that could allow for escalation of privilege. (CVE-2024-53104, CVE-2025-0088)
Details of lower-severity vulnerabilities are as follows:
- Multiple vulnerabilities in Framework that could allow for information disclosure. (CVE-2023-40122, CVE-2023-40133, CVE-2023-40134, CVE-2023-40135, CVE-2023-40136, CVE-2023-40137, CVE-2023-40138, CVE-2023-40139, CVE-2024-0037, CVE-2025-0100)
- A vulnerability in Framework that could allow for denial of service. (CVE-2024-49741)
- Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2024-49723, CVE-2024-49729)
- A vulnerability in Google Play system updates. (CVE-2024-49723)
- A vulnerability in Arm components. (CVE-2025-0015)
- Multiple vulnerabilities in Imagination Technologies. (CVE-2024-43705, CVE-2024-46973, CVE-2024-47892, CVE-2024-52935)
- Multiple vulnerabilities in MediaTek components. (CVE-2025-20634, CVE-2024-20141, CVE-2024-20142, CVE-2025-20635, CVE-2025-20636)
- A vulnerability in Unisoc components. (CVE-2024-39441)
- Multiple vulnerabilities in Qualcomm components. (CVE-2024-45569, CVE-2024-45571, CVE-2024-45582, CVE-2024-49832, CVE-2024-49833, CVE-2024-49834, CVE-2024-49839, CVE-2024-49843)
- Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2024-38404, CVE-2024-38420)
Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation in the context of the affected component. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
- Apply appropriate mitigations 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.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.
- 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 Apple® System Integrity Protection (SIP) and Gatekeeper™.
- Safeguard 13.10 : Perform Application Layer Filtering: Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or gateway.
- Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)
- Safeguard 16.8: Separate Production and Non-Production Systems: Maintain separate environments for production and non-production systems
REFERENCES:
Android:
https://source.android.com/docs/security/bulletin/2025-02-01
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40122
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40133
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40134
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40135
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40136
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40137
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40138
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40139
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0037
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20141
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20142
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38404
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-38420
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39441
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43705
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45569
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45571
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-45582
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46973
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47892
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49721
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49723
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49723
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49729
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49741
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49743
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49746
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49832
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49833
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49834
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49839
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49843
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-52935
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53104
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0015
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0088
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0091
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0094
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0095
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0099
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0100
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-20634
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-20635
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-20636