Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain privileged host access
-
ExploitLocate writable root filesystem
-
ExecutionModify critical system files/config
-
ImpactTamper with or compromise host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V13 - Configuration Secure default settings
|
| Exploitation Conditions | Requires that the BigFix Service Management (v23) host be deployed with its root filesystem writable rather than mounted read-only (the default/misconfigured state described), AND that an attacker already possess high privileges on that host (PR:H) to perform the unintended modifications. There is no user interaction required, but the flaw is a hardening deficiency that amplifies an existing foothold rather than granting initial access; it is not independently triggerable by an unauthenticated remote request despite the AV:N label. |
| Impact | This is a low-priority, defense-in-depth hardening finding despite its 7.2 (High) CVSS. The signals are consistent and point away from urgency: EPSS is 0.03% (8th percentile), there is no CISA KEV listing, no public POC, and SSVC scores it Exploitation:none / Automatable:no / Technical Impact:partial. The most important tension is between the CVSS vector and the weakness itself: the vector claims AV:N (network) with C:H/I:H/A:H, but the description (CWE-1188, root file system not mounted read-only) is a system-hardening misconfiguration that enables *unintended modifications* once an actor already has sufficient access - reflected in the PR:H requirement. An improperly mounted (writable) root FS is not itself a remotely triggerable exploit; it is a condition that amplifies the impact of some *other* foothold. The AV:N/high-CIA framing therefore overstates standalone remote risk - verify with HCL whether any network-facing path actually leverages this. Net: real risk is low and contingent on an attacker first obtaining privileged/local access. |
| Exploit ScenarioDerived | An attacker who has already obtained privileged access to a BigFix Service Management host (e.g., via a separate compromise or an over-privileged service account) leverages the writable root filesystem to modify critical system binaries or configuration that should have been immutable, cementing control or tampering with the appliance. No public exploit code exists, and the flaw cannot be triggered without that pre-existing high-privilege foothold. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 30, 2026
HCL BigFix Service Management (SM) version 23 ships with - or can be deployed in - a state where the host root filesystem is mounted writable instead of read-only, allowing an attacker who already holds high privileges on that host to modify critical system components that should be immutable. The impact is a hardening deficiency that amplifies an existing foothold rather than a way to gain initial access: remediation requires prior high-privileged (PR:H) access to the local host, and no public exploit code or confirmed active exploitation exists (EPSS 0.03%, 8th percentile; SSVC Exploitation: none, Automatable: no, Technical Impact: partial). This is best treated as a low-priority, defense-in-depth finding despite its 7.2 (High) nominal CVSS.
Earlier versions of this analysis (1)
HCL BigFix Service Management is vulnerable to improper root filesystem configuration, allowing high-privileged authenticated users with user interaction to make unauthorized modifications to critical system components. The vulnerability requires administrative privileges and user consent (CVSS:3.1/AV:N/AC:H/PR:H/UI:R), resulting in limited confidentiality, integrity, and availability impacts. No active exploitation has been publicly reported.
RemediationAI
Patch available per vendor advisory: consult and apply the HCL fix referenced in knowledge-base article KB0128144 (https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0128144); no exact patched build version is stated in the supplied data, so verify the applicable release with HCL before upgrading. As a direct compensating control independent of the patch, mount the root filesystem read-only (for example, set 'ro' on the '/' entry in /etc/fstab and remount, or boot the BigFix SM appliance with the root volume read-only) so that critical system components cannot be modified at runtime; the trade-off is that legitimate administrative changes then require an explicit remount/reboot window, and some installers or updates may fail until the volume is temporarily made writable. Where read-only root is not operationally feasible, restrict and monitor who can obtain root on the BigFix SM host (treat root access as a privileged, audited action), enable file-integrity monitoring on system binaries and service configuration, and confirm BigFix SM hosts are not exposed to untrusted networks. If any enforcement is deferred because of operational side effects, document the compensating controls and re-evaluate the writable-root configuration at the next maintenance window.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-1188 (Insecure Default Initialization of Resource) and concerns operating-system hardening rather than a memory-safety or injection bug: the underlying root filesystem of the BigFix Service Management (SM) v23 host is not mounted read-only, so files and directories that ought to be immutable can be written to at runtime. Because the CPE string (cpe:2.3:a:hcl_software:bigfix_service_management_(sm):*:*:*:*:*:*:*:*) is unversioned beyond the SM product family, the affected surface is the BigFix SM server/appliance operating environment itself. Note the divergence between the published vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and the independent assessment (AV:L, PR:H): despite the AV:N label, the issue is a local configuration/hardening condition triggered only by a principal that already possesses high privileges on the host, not by an unauthenticated remote request. Exploitation yields high confidentiality, integrity, and availability impact within the same security scope because writable root allows tampering with binaries, configuration, and service components.
Know when Bigfix Service Management Sm gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
A writable-root-FS hardening flaw is exercised locally by an already-privileged actor, so AV:L and PR:H; once abused it permits modification of critical system components, hence C/I/A:H.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
HCL BigFix Service Management (SM) is susceptible to a Root File System Not Mounted as Read-Only. An improperly configured root file system may allow
unintended modifications to critical system components, potentially increasing the risk of system compromise or unauthorized changes.
Executive ViewAI
HCL BigFix Service Management version 23 can be deployed with a writable root filesystem, allowing an attacker who already holds high-privileged local access to modify system components that should be immutable. This is a hardening deficiency that could help an existing foothold persist or evade defenses, rather than a means of initial compromise. Leadership should treat it as a defense-in-depth risk for environments running BigFix SM v23, with no public exploit identified at time of analysis.
No vendor-released patch is available. Enforce least privilege, restrict and monitor local root/administrator access, implement file-integrity monitoring on critical system components, remount the root filesystem read-only where operationally feasible, and apply vendor hardening guidance when published.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Bigfix Service Management Sm
View allHCL BigFix Service Management (SM) version 23 ships with an outdated, vulnerable WSGI (Web Server Gateway Interface) ser
HCL BigFix Service Management (SX) is affected by a Broken Access Control vulnerability leading to privilege escalation.
HTTP request smuggling in HCL BigFix Service Management (SM) 23 allows unauthenticated remote attackers to bypass front-
Credential exposure in HCL BigFix Service Management (SM) version 23 leaves credentials insufficiently protected for a b
HCL BigFix Service Management contains unauthenticated-accessible directories that are not linked in the user interface
HCL BigFix Service Management (SM) contains a cross-site request forgery (CSRF) vulnerability that allows authenticated
HCL BigFix Service Management lacks secure X-Content-Type-Options HTTP headers, allowing browsers to perform MIME-type s
HCL BigFix Service Management (SM) leaks sensitive information through improper error handling in its reporting module.
HCL BigFix Service Management exposes server banner information containing software versions and system details accessib
HCL BigFix Service Management Discovery accepts unencrypted HTTP traffic on port 80, allowing network-adjacent attackers
HCL BigFix Service Management (SM) contains a Content Security Policy (CSP) header misconfiguration that enables cross-s
HCL BigFix Service Management fails to sanitize spreadsheet data (CSV, XLS, XLSX) before export, allowing authenticated
EUVD-2025-209705
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB