dbcve.org
Bigfix MobileApplication · Hcltech

CVE-2025-0277

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 3.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HCL BigFix Mobile 3.3 and earlier are vulnerable to certain insecure directives within the Content Security Policy (CSP). An attacker could trick users into performing actions by not properly restricting the sources of scripts and other content.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HCL BigFix Mobile 3.3 and earlier versions contain a Content Security Policy (CSP) misconfiguration where insecure directives fail to properly restrict the sources of scripts and other content. This allows attackers to potentially inject malicious scripts or content from untrusted origins, leading to XSS or content injection attacks.

MitigationUpdate HCL BigFix Mobile to version 3.4 or later to receive the patched CSP configuration, or manually review and harden CSP headers to remove unsafe directives like 'unsafe-inline', 'unsafe-eval', or overly permissive wildcard sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bigfix MobileApplication
Affected:<= 3.3
Bigfix Modern Client ManagementApplication
Affected:< 3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed BigFix product and version
    Use your system's package manager, software inventory, or the BigFix admin console to determine whether HCL BigFix Mobile or BigFix Modern Client Management is installed, and note its exact version number.
    Affected if The installed version is BigFix Mobile at 3.3 or earlier, or BigFix Modern Client Management at any version below 3.4.
  2. Locate CSP configuration or response headers
    If you have access to the BigFix server or web interface logs, capture HTTP responses from the BigFix application using a browser dev tool or a proxy like Burp or curl, focusing on the Content-Security-Policy HTTP header.
    Affected if The application returns a Content-Security-Policy header that contains the CSP misconfiguration.
  3. Inspect for unsafe-inline or unsafe-eval directives
    Examine the CSP header value for the presence of 'unsafe-inline' or 'unsafe-eval' directives, which allow inline scripts or dynamic code execution from untrusted sources.
    Affected if The CSP header contains 'unsafe-inline' or 'unsafe-eval', which weakens script restrictions.
  4. Check for overly permissive source Allowlists
    Review the CSP header for wildcard sources (such as '*', '*.example.com', or overly broad domain patterns) in script-src, style-src, img-src, or other content directives.
    Affected if The CSP allows content from wildcard or untrusted domains, enabling injection from arbitrary origins.

You are affected if BigFix Mobile is at version 3.3 or earlier (or Modern Client Management is below 3.4) AND the CSP header contains insecure directives like unsafe-inline, unsafe-eval, or overly permissive source Allowlists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4 or later
Fixed in 3.4
Interim mitigation

Update HCL BigFix Mobile to version 3.4 or later to receive the patched CSP configuration, or manually review and harden CSP headers to remove unsafe directives like 'unsafe-inline', 'unsafe-eval', or overly permissive wildcard sources.

Recommended fix Moderate confidence

BigFix Mobile: 3.4 or later | BigFix Modern Client Management: 3.4 or later

  1. 1. Identify the current BigFix Mobile and/or BigFix Modern Client Management version in your environment
  2. 2. Access HCL support portal at support.hcl-software.com to obtain the version 3.4 or later installation packages
  3. 3. Review HCL BigFix upgrade documentation for your specific product
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Backup current configuration and database as recommended in HCL documentation
  6. 6. Install BigFix Mobile version 3.4 or later, or BigFix Modern Client Management version 3.4 or later
  7. 7. Verify the upgrade was successful by checking the product version
  8. 8. Validate that CSP headers are now properly configured by reviewing server responses
Caveat Review HCL release notes for version 3.4 for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bigfix Mobile Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0277 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data