dbcve.org
Bigfix PlatformApplication · Hcltech

CVE-2023-37519

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 9.5.23 / 10.0.10 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
Unauthenticated Stored Cross-Site Scripting (XSS) vulnerability. This XSS vulnerability is in the Download Status Report, which is served by the BigFix Server. 

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

Unauthenticated Stored Cross-Site Scripting (XSS) vulnerability in the Download Status Report component of the BigFix Server allows remote attackers to inject malicious scripts that are stored and executed when users view the affected report.

MitigationImplement proper input validation and output encoding/sanitization on all user-controllable data displayed in the Download Status Report to prevent script injection.

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.23>= 10.0.0, < 10.0.10= 11.0.0

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 BigFix Server installation and version
    Locate the BigFix Server installation directory and check the version file, or run 'BESServer.exe -version' or check the BigFix Administration Tool for the server version
    Affected if Version matches >=9.5 and <9.5.23, or >=10.0.0 and <10.0.10, or equals 11.0.0
  2. Confirm Download Status Report component is accessible
    Access the BigFix Web Reports interface and navigate to the Download Status Report, or verify the web reports endpoint is exposed at /webreports/ or similar
    Affected if The Download Status Report web interface is accessible and the server version is in the affected range
  3. Check for recent XSS indicators in web logs
    Review BigFix server web logs (typically in the BESServer\WebReports\logs directory) for suspicious patterns in Download Status Report parameters, such as script tags or javascript: URIs in fields that should be text-only
    Affected if Malicious script payloads are present in the logs indicating the vulnerability has been exploited

Your environment is affected if the BigFix Server version is 9.5 through 9.5.22, 10.0.0 through 10.0.9, or exactly 11.0.0, and the Download Status Report web component is accessible.

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 9.5.23 / 10.0.10 or later
Fixed in 9.5.2310.0.10
Interim mitigation

Implement proper input validation and output encoding/sanitization on all user-controllable data displayed in the Download Status Report to prevent script injection.

Recommended fix Moderate confidence

BigFix Platform 9.5.23 (for 9.5.x), 10.0.10 (for 10.0.x), or 11.0.1+ (for 11.x)

  1. 1. Identify your current BigFix Platform version by accessing the BigFix console and checking the version information in the Help > About BigFix menu.
  2. 2. Based on your current version, determine the appropriate upgrade path: If running 9.5.x series (version >= 9.5 and < 9.5.23), upgrade to version 9.5.23 or later.
  3. 3. If running 10.0.x series (version >= 10.0.0 and < 10.0.10), upgrade to version 10.0.10 or later.
  4. 4. If running version 11.0.0, upgrade to the next available patch version (11.0.1 or later).
  5. 5. Obtain the appropriate upgrade package from the HCL BigFix support portal or authorized distribution channel.
  6. 6. Before applying the upgrade, perform a complete backup of the BigFix database and configuration files.
  7. 7. Schedule a maintenance window as upgrades may require downtime.
  8. 8. Follow the official HCL BigFix upgrade documentation to apply the patch, ensuring you follow pre-upgrade checks and post-upgrade validation steps.
Caveat Review HCL BigFix release notes for your specific upgrade path for any known compatibility issues or configuration changes required

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

Fix this in Bigfix Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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