dbcve.org
Bigfix PlatformApplication · Hcltech

CVE-2022-27545

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to after 10.0.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
BigFix Web Reports authorized users may perform HTML injection for the email administrative configuration page.

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 · high confidence

This is an HTML injection vulnerability in BigFix Web Reports where authenticated users can inject arbitrary HTML into the email administrative configuration page. The vulnerability stems from insufficient input sanitization or output encoding when handling user-supplied data in that specific page.

MitigationImplement proper input validation and output encoding for all user-supplied data in the email administrative configuration page to prevent HTML injection. Apply context-aware escaping before rendering any user input in HTML contexts.

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 PlatformApplication
Affected:>= 9.5, <= 9.5.19>= 10.0, <= 10.0.6

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Platform version
    Locate the BigFix installation directory and check the version information file, or use the BigFix console to view the version under the Help > About section
    Affected if The version falls within 9.5 through 9.5.19 or 10.0 through 10.0.6
  2. Confirm Web Reports component is installed
    Check for the presence of the Web Reports module in the BigFix installation, typically found under the WebReports folder in the installation directory
    Affected if Web Reports is installed and the version is in the affected range
  3. Verify the email administrative configuration page is accessible
    Access the Web Reports administrative interface and navigate to the email configuration section, typically found under Settings or Administration menus
    Affected if The email configuration page is accessible and user authentication is enabled
  4. Check if external authentication or weak authentication is configured
    Review the authentication settings in the Web Reports configuration to determine if authenticated users have access to the email administrative settings
    Affected if Authenticated users can access the email administrative configuration page without additional security restrictions

Your environment is affected if BigFix Platform version is between 9.5 and 9.5.19 or between 10.0 and 10.0.6, Web Reports is installed, and the email administrative configuration page is accessible to authenticated users.

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 a release after 10.0.6
Interim mitigation

Implement proper input validation and output encoding for all user-supplied data in the email administrative configuration page to prevent HTML injection. Apply context-aware escaping before rendering any user input in HTML contexts.

Recommended fix Moderate confidence

Version 9.5.20 or later, or version 10.0.7 or later (check HCL support for exact fixed release)

  1. Check current BigFix Platform version in the Web Reports administration console or via the BigFix Administration Tool
  2. Navigate to HCL Support portal (support.hcltechsw.com) and search for CVE-2022-27545 to obtain the exact patch or fixed version
  3. If running version 9.5.x: upgrade to version 9.5.20 or later (or the latest 9.5.x release)
  4. If running version 10.0.x: upgrade to version 10.0.7 or later (or the latest 10.0.x release)
  5. After upgrade, verify the email administrative configuration page is accessible and functions correctly
  6. Confirm the HTML injection vulnerability is resolved by testing the email configuration page with the previously problematic input
Caveat Review HCL release notes for the target version for any configuration or feature changes that may affect existing deployments

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

Fix this in Bigfix Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27545 — 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-2022-27545 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