CVE-2023-37520
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 · uneditedUnauthenticated Stored Cross-Site Scripting (XSS) vulnerability identified in BigFix Server version 9.5.12.68, allowing for potential data exfiltration. This XSS vulnerability is in the Gather Status Report, which is served by the BigFix Relay.
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 confidenceUnauthenticated stored XSS vulnerability in BigFix Server v9.5.12.68 in the Gather Status Report feature served by BigFix Relay. Attackers can inject malicious scripts that persist on the server and execute in users' browsers, potentially leading to session hijacking and data exfiltration.
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>= 9.5, < 9.5.23>= 10.0.0, < 10.0.10= 11.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify BigFix Platform versionRun the command 'BESServer.exe -version' or check the BigFix Server version through the BigFix Administration tool under Server Settings. On the server, also check the registry key HKLM\SOFTWARE\BigFix\Enterprise Server\CurrentVersion or inspect the installation directory for version info in the server's about page.Affected if The installed version falls within >= 9.5 and < 9.5.23, or >= 10.0.0 and < 10.0.10, or exactly version 11.0.0
-
Verify BigFix Relay is enabledCheck the BigFix Relay configuration by logging into the BigFix console, navigating to the Relay Settings under the Relay tab, or by inspecting the server's configuration file at <BESServerInstallDir>\BES Relay\cfgrelay.txt or the Web Reports configuration.Affected if BigFix Relay is running and serving content to clients, which is required for the Gather Status Report feature to be exposed
-
Confirm Gather Status Report feature is accessibleAccess the Gather Status Report endpoint on the Relay. The feature is typically accessible at URLs like http://<relay_host>:52311/cgi-bin/bfgather.exe/gatherstatus or through the BigFix Relay status page. Check if this endpoint returns a status report page.Affected if The Gather Status Report feature is enabled and accessible via the Relay, which is the vulnerable component
-
Inspect Gather Status Report for injected scriptsView the HTML source of the Gather Status Report page served by the Relay. Look for any script tags, event handlers (onclick, onerror, etc.), or suspicious iframe/embed tags in the page content. Compare against expected baseline content.Affected if Malicious JavaScript code or unexpected script tags appear in the Gather Status Report output, indicating exploitation has occurred
You are affected if your BigFix Platform version is 9.5 through 9.5.22, 10.0.0 through 10.0.9, or exactly 11.0.0, AND the BigFix Relay with Gather Status Report feature is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.5.2310.0.10
Apply vendor-provided patch/update for BigFix Server version 9.5.12.68 to address input validation in the Gather Status Report component; review and sanitize any custom configurations in the meantime.
BigFix 9.5.23, 10.0.10, or 11.0.1+ (latest available)
- 1. Identify the current BigFix Server and Relay versions deployed in your environment
- 2. For BigFix 9.5.x deployments: Upgrade to version 9.5.23 or later
- 3. For BigFix 10.0.x deployments: Upgrade to version 10.0.10 or later
- 4. For BigFix 11.0.0 deployments: Upgrade to version 11.0.1 or later (the latest available HCL release)
- 5. After upgrading, verify the Gather Status Report functionality is working correctly and the XSS vulnerability is remediated
- 6. Verify all BigFix Relays are also updated to the same fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-37520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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