Release Date: September 29, 2025
Bulletin ID: AWCB-2025-39
Product: HySecure 7.x (Multiple Versions)

 

Executive Summary

Low Risk - No Immediate Action Required

Objective: This advisory notifies customers of known security vulnerabilities associated with HySecure, outlines our evaluation and analysis, and proposes a recommended action plan.

Key Points for System Administrators:

  • 61 new CVEs identified - assessed with minimal impact to HySecure deployments

  • No critical vulnerabilities require immediate attention in HySecure operations

  • Scheduled patching: October 2025 monthly release cycle (vulnerabilities identified after September 3)

  • Current deployments maintain security with existing configurations

Immediate Actions Required: None

Recommended Actions:

  • Schedule the October 2025 update during the standard maintenance window

  • Review mitigation factors below for specific vulnerabilities

  • Continue following standard security hardening practices


Vulnerability Assessment Summary [22/09/2025 – 29/09/2025]

Assessment based on HySecure architecture and deployment context

 Remediation Path  Critical  High  Medium  Low  Info  Total  Admin Impact 
 Emergency Patch  0  0  0  0  0  0  No immediate action needed 
 Monthly Patch  0  5  56  0  0  61  Schedule October update 
 Not Applicable  0  0  0  0  0  0  Components not present 
 Deferred  0  1  0  0  0  1  Monitor future releases 

 

Vulnerability Summary for Previous Weeks Identified CVEs (After SF08 as of September 29, 2025)

 CVE Bulletins   Critical  High  Medium  Low  Info  Total Status
AWCB-2025-37 (08/09/2025 – 15/09/2025)   0  2  122  0  0  124 Scheduled for October Patch  
AWCB-2025-38 (15/09/2025 – 22/09/2025)  0  0  0  0  0  0N/A


Risk Assessment Context:

Critical and high-severity vulnerabilities were assessed for their impact on the HySecure product. Based on our analysis, we have revised the severity of these vulnerabilities for HySecure deployments.

Severity Definitions:

  • Critical: Exploitable remotely with severe impact (RCE, privilege escalation)

  • High: High probability of exploitation or significant business impact

  • Medium: Exploitable under specific conditions; limited impact

  • Low: Low likelihood of exploitation; minor impact

  • Informational: No direct risk; potential hardening opportunities

 

Quick Reference for System Administrators

1. Do I Need to Take Action Today?

  • No - Continue normal operations

2. When Should I Schedule Updates?

  • October 2025 Monthly Release - Plan during next maintenance window

3. How Do I Verify My Environment is Secure?

  • Check HySecure version: The HySecure version and status can be checked from the management console dashboard. Make sure you are on the latest version.

  • Verify firewall rules: Confirm if only the required ports are exposed

  • Review access logs: Look for unusual connection patterns

  • Validate configuration: Run standard security audit checklist

4. What Components Are Affected?

  • cups (Print Service) - Not configured for remote connections in HySecure

  • systemd - Internal components with minimal exposure

  • Kernel-uek, MariaDB - Internal components not exposed to external networks

 

Detailed Vulnerability Analysis

High Severity Vulnerabilities: 5 → Revised Severity: low

1. gnutls

  • CVE IDs: CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-6395

  • CVE Details:

            All the above CVEs are discovered in the GnuTLS (GNU Transport Layer Security Library) software. These vulnerabilities primarily lead to Denial of Service (DoS) due to memory corruption issues. 

  • Original Severity: High
  • HySecure Revised Severity: low

    Why This Has Minimal Impact on HySecure:

  • Limited Exposure (CVE-2025-32990): The vulnerability affects the certtool utility, which is a local, administrative command-line tool and is not exposed to the public network, making remote exploitation impossible. 

  • Security Hardening (CVE-2025-32988, -32989): Memory corruption flaws are highly unlikely to be exploited for arbitrary code execution because HySecure operates on a hardened OS that employs mitigations like ASLR (Address Space Layout Randomization). 

  • Low DoS Impact (CVE-2025-6395): The Denial of Service (DoS) flaw causes a process crash, but HySecure's robust architecture ensures the affected process is immediately restarted, resulting in minimal service downtime. 

  • Trusted Certificate Usage (CVE-2025-32988, -32989): As a gateway, HySecure primarily processes certificates from trusted sources (e.g., internal servers or public CAs), severely limiting an attacker's ability to introduce the malformed certificates required to trigger the parsing vulnerabilities.

2. python-cryptography

  • CVE ID: CVE-2023-49083

  • CVE Details:

            NULL-pointer dereference in the load_pem_pkcs7_certificates or load_der_pkcs7_certificates functions when deserializing a malformed PKCS7 certificate. This flaw leads to a segmentation fault and causes a Denial of Service (DoS) for the affected Python application. 

  • Original Severity: High

  • HySecure Revised Severity: low

Why This Has Minimal Impact on HySecure:

  • Limited Exposure to Untrusted Input: The vulnerability is triggered by parsing specially crafted PKCS7 certificates/blobs. In the HySecure gateway, PKCS7 certificate parsing is not a routine operation exposed 

  • No Code Execution Risk: This is a Null Pointer Dereference (CWE-476), which almost exclusively results in a crash (DoS). The potential for an attacker to escalate this to arbitrary code execution is considered negligible in a modern, hardened appliance environment like HySecure. 


Medium Severity Vulnerabilities: 56 → Revised Severity: low

1. Kernel-uek (Oracle Enterprise Kernel)

  • CVE ID: CVE-2025-38264, CVE-2025-38494, CVE-2025-38495, CVE-2025-38499, CVE-2025-38618 
  • CVE Details:

            Multiple kernel vulnerabilities: Various memory corruption, privilege escalation, and denial of service vulnerabilities in Oracle Enterprise Kernel subsystems

  • Original Severity: Medium

  • HySecure Revised Severity: low

    Why This Has Minimal Impact on HySecure:

  • Local access required: Listed CVEs require local access, specific configurations, or enabled features not present in HySecure

  • Not exposed: Features and configurations vulnerable to these CVEs are not enabled or exposed in the HySecure deployment

  • Controlled environment: HySecure operates in controlled network environments, reducing exploitation opportunities

2. mysql

  • CVE IDs: CVE-2025-21574,CVE-2025-21575,CVE-2025-21577,CVE-2025-21579,CVE-2025-21580,CVE-2025-21581,CVE-2025-21584,CVE-2025-21585,CVE-2025-30681,CVE-2025-30682,CVE-2025-30683,CVE-2025-30684,CVE-2025-30685,CVE-2025-30687,CVE-2025-30688,CVE-2025-30689,CVE-2025-30693,CVE-2025-30695,CVE-2025-30696,CVE-2025-30699,CVE-2025-30703,CVE-2025-30704,CVE-2025-30705,CVE-2025-30715,CVE-2025-30721,CVE-2025-30722,CVE-2025-50077,CVE-2025-50078,CVE-2025-50079,CVE-2025-50080,CVE-2025-50081,CVE-2025-50082,CVE-2025-50083,CVE-2025-50084,CVE-2025-50085,CVE-2025-50086,CVE-2025-50087,CVE-2025-50088,CVE-2025-50091,CVE-2025-50092,CVE-2025-50093,CVE-2025-50094,CVE-2025-50096,CVE-2025-50097,CVE-2025-50098,CVE-2025-50099,CVE-2025-50100,CVE-2025-50101,CVE-2025-50102,CVE-2025-50104,CVE-2025-53023
  • CVE Details:

           Above CVEs affects components like the Server Parser, Replication, Optimizer, and MySQL Cluster, most of which could lead to Denial of Service (high impact on availability). While some flaws were exploitable by low-privileged users, others required high privileges with network access. Overall, the critical issues mainly affected system availability, with little to no impact on confidentiality or integrity. 

  • Original Severity: Medium

  • HySecure Revised Severity: low

    Why This Has Minimal Impact on HySecure:

  • HySecure remains minimally impacted by MySQL vulnerabilities due to its hardened Linux-based architecture, restricted administrator-only access, and absence of unprivileged users. The embedded MySQL database is isolated, used only for internal configuration and logging, and not exposed to end-users or the internet, significantly reducing exploitation vectors. Most vulnerabilities focus on Denial of Service (DoS), but exploitation typically requires high privileges, and HySecure’s high-availability clustering further mitigates potential downtime. 

 

Administrator Action Plan

October 2025 Release Planning

  • Target Release Date: October 31, 2025

  • Maintenance Window Required: 2-4 hours (standard update process)

  • Security Hotfix ID: AH_OL9_CM_SF09


Pre-Update Checklist:

  • Backup current configuration: Navigate to Settings > General Settings > Backup & Restore. In the Backup section, select the option Backup User Settings Only and click Submit to download the User Backup file.

  • Verify system resources: Ensure adequate disk space and memory

  • Schedule maintenance window: Coordinate with stakeholders

  • Test connectivity: Confirm clients can reconnect post-update


Post-Update Verification:

  • Check service status: Log on to the Management console. Go to Diagnose > Services Status.

  • Verify client connectivity: Test from multiple client types

  • Review logs: Check for errors or warnings

  • Validate security settings: Run security configuration audit


Verification Commands:

1. Check HySecure version and status

  • The HySecure version and status can be checked from the management console dashboard

2. Verify if the security update is applied properly


Deferred Issue Monitoring

One vulnerability deferred to future OS release:

  • Component: systemd

  • Monitoring: Will be addressed in subsequent Linux distribution updates

  • Action: Continue standard patching cycles


Customer Guidance

Deployment Security:

  • Keep deployment updated with the latest HySecure versions and patches

  • Implement network segmentation - ensure HySecure components are not directly internet-accessible

  • Enable comprehensive logging and review access patterns regularly

  • Follow the principle of least privilege for accounts and services

  • Apply security hardening as documented in the HySecure Security Configuration Guide


Support and Contact Information

For Technical Questions:

  • Email: support@accops.com

  • Subject Line: "AWCB-2025-37 - $Your Question$"

  • Include: HySecure version, deployment details, specific concerns

For Patch Scheduling Assistance:

  • Contact your assigned Customer Success Manager

  • Reference the latest security hotfix for scheduling guidance

Emergency Security Issues:

  • Email: security@accops.com

  • Phone: Contact customer support for immediate escalation

  • Available: 24/7 through customer support channels


For the most current information and updates, visit: https://www.accops.com/product-software