dbcve.org
Bigfix Bare Osd Metal Server WebuiApplication · Hcltechsw

CVE-2023-37521

MEDIUM · 5.3 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 311.28 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Bare OSD Metal Server WebUI version 311.19 or lower can sometimes include sensitive information in a query string which could allow an attacker to execute a malicious attack.

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 Bare OSD Metal Server WebUI version 311.19 and earlier contains a sensitive information disclosure vulnerability where sensitive data is transmitted via query string parameters. This exposure could allow attackers to capture credentials, session tokens, or other sensitive data through malicious links, server logs, or browser history.

MitigationUpgrade to a version higher than 311.19 and implement secure handling of sensitive parameters (use POST instead of GET, encrypt query parameters, or avoid including sensitive data in URLs entirely).

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 Bare Osd Metal Server WebuiApplication
Affected:< 311.28

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if HCL BigFix Bare OSD Metal Server WebUI is installed
    Locate the BigFix installation directory or check installed programs on the server. The WebUI component is typically found within the BigFix server installation.
    Affected if The software is present on the system
  2. Determine the installed version of the BigFix Bare OSD Metal Server WebUI
    Check the version information for the WebUI component. This may be available in the installation logs, version file, or via the BigFix administration console. Compare your version against the affected range: version 311.19 or earlier.
    Affected if The installed version is 311.19 or earlier, or any version below 311.28
  3. Verify if the WebUI is network-accessible
    Confirm that the BigFix WebUI is exposed to network access, either internally or externally. Check firewall rules and WebUI binding configuration.
    Affected if The WebUI is accessible over the network
  4. Inspect server access logs for sensitive data in query strings
    Review web server logs (IIS, Apache, or BigFix native logs) for URLs containing sensitive-looking parameters such as passwords, tokens, session IDs, or credentials passed via GET requests.
    Affected if Logs contain URLs with sensitive parameters in query strings

A user is affected if the BigFix Bare OSD Metal Server WebUI version is 311.19 or earlier (below 311.28) and the WebUI is accessible, with sensitive data potentially exposed in query string parameters.

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 311.28 or later
Fixed in 311.28
Interim mitigation

Upgrade to a version higher than 311.19 and implement secure handling of sensitive parameters (use POST instead of GET, encrypt query parameters, or avoid including sensitive data in URLs entirely).

Recommended fix High confidence

311.28

  1. Back up the current BigFix Bare OSD Metal Server WebUI configuration and data
  2. Download HCL BigFix Bare OSD Metal Server WebUI version 311.28 from the official HCL support portal (support.hcltechsw.com)
  3. Apply the upgrade to the BigFix Bare OSD Metal Server WebUI instance following the documented upgrade procedure
  4. Verify the upgrade was successful by checking the WebUI version and confirming the application is functioning properly

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

Fix this in Bigfix Bare Osd Metal Server Webui Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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